Overview
| Artifact ID: | 1a848292e555c607e897a2ad8445e491e8f51878 |
|---|---|
| Ticket: | 5b2cffd17c9da4ea8053cc5383925a372220e221
Variables in one target with no value produce "<var>=" in another target's test's env |
| User & Date: | mmgraham on 2022-06-22 15:35:36 |
Changes
- comment changed to:
When a variable is defined in a target earlier in the runconfig file, with no value, like MYENVVAR it appears with the name "MYENVVAR=" in the environment of a test run from a later target in the runconfig. It does not appear when doing megatest -show-runconfig -target <target> The workaround is to put "" for the value of the var.
- foundin changed to: "1.65/92"
- login: "mmgraham"
- private_contact changed to: "0b858582443dd43746dc236c08b062c9b6a8cf86"
- severity changed to: "Important"
- status changed to: "Open"
- title changed to:
Variables in one target with no value produce "<var>=" in another target's test's env
- type changed to: "Code_Defect"