|
2022-06-22
| ||
| 15:35 | • New ticket [5b2cffd17c] Variables in one target with no value produce "<var>=" in another target's test's env. artifact: 1a848292e5 user: mmgraham | |
| Ticket Hash: | 5b2cffd17c9da4ea8053cc5383925a372220e221 | |||
| Title: | Variables in one target with no value produce "<var>=" in another target's test's env | |||
| Status: | Open | Type: | Code_Defect | |
| Severity: | Important | Priority: | ||
| Subsystem: | Resolution: | |||
| Last Modified: | 2022-06-22 15:35:36 | |||
| Version Found In: | 1.65/92 | |||
| Description: | ||||
|
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. | ||||