|
2015-09-08
| ||
| 09:28 | • Ticket [b535d2274f] items not applied across multiple waitons status still Open with 5 other changes artifact: 5d5474399f user: tyardeni | |
| 09:21 | • New ticket [b535d2274f]. artifact: 33e4f2bc0b user: tyardeni | |
| Ticket Hash: | b535d2274fcc6fdb4183b9045734954ac606e344 | |||
| Title: | items not applied across multiple waitons | |||
| Status: | Open | Type: | Code_Defect | |
| Severity: | Severe | Priority: | Immediate | |
| Subsystem: | Resolution: | Open | ||
| Last Modified: | 2015-09-08 09:28:49 | |||
| Version Found In: | 1.6023 | |||
| Description: | ||||
| With multiple waiton dependencies, the items are applied only to the last waiton dep. | ||||
| User Comments: | ||||
|
tyardeni added on 2015-09-08 15:28:49:
I have the following sequence of tests, all configured with items: item.0 item.1 test0 test1 test2 test3 test4 test4a seq4 Each has the following requirements: [requirements] mode itemwait waiton test[n-1][requirements] mode itemwait waiton test4 test4a And test4a depends on test3. If I run with testpatt: seq4/item.1 I expect to see the following run: test0/item.1 test1/item.1 test2/item.1 test3/item.1 test4/item.1 test4a/item.1 seq4/item.1 Instead I see: test0/item.1 test0/item.0 test1/item.1 test1/item.0 test2/item.1 test2/item.0 test3/item.1 test3/item.0 test4/item.1 test4/item.0 test4a/item.1 seq4/item.1 There is a test in megatest_qa (chained-waiton) that catches this condition. | ||||