Artifacts Associated With Ticket b535d2274f
Ticket change [33e4f2bc0b] (rid 9740) by tyardeni on 2015-09-08 09:21:41:
- comment initialized to:
With multiple waiton dependencies, the items are applied only to the last waiton dep.
- foundin initialized to: "1.6023"
- login: "tyardeni"
- private_contact initialized to: "97a985880d55d4326aae6748098171ce1de44344"
- severity initialized to: "Severe"
- status initialized to: "Open"
- title initialized to: "items not applied across multiple waitons"
- type initialized to: "Code_Defect"
- comment initialized to:
Ticket change [5d5474399f] (rid 9741) by tyardeni on 2015-09-08 09:28:49:
- icomment:
I have the following sequence of tests, all configured with items: item.0 item.1 <verbatim> test0 test1 test2 test3 test4 test4a seq4 </verbatim> Each has the following requirements: <verbatim> [requirements] mode itemwait waiton test[n-1] </verbatim Except for seq4 which has the following requirements: <verbatim> [requirements] mode itemwait waiton test4 test4a </verbatim> And test4a depends on test3. If I run with testpatt: seq4/item.1 I expect to see the following run: <verbatim> test0/item.1 test1/item.1 test2/item.1 test3/item.1 test4/item.1 test4a/item.1 seq4/item.1 </verbatim> Instead I see: <verbatim> 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 </verbatim> There is a test in megatest_qa (chained-waiton) that catches this condition.
- login: "tyardeni"
- mimetype: "text/x-fossil-wiki"
- priority changed to: "Immediate"
- resolution changed to: "Open"
- icomment: