Using this series configuration below, when I submit "pav series run compute", test_a and test_b both run sequentially as expected (testing one node only by design), but the stage_two_tests never run or are queued. If I do "pav wait s####", I see the test_a and test_b status periodically update, but no other tests. Is this a bug or am I doing something incorrectly? Also the python process associated with the series job continues to run long after test_a and test_b have completed. The same problem is seen running under the latest/master tree.
Using this series configuration below, when I submit "pav series run compute", test_a and test_b both run sequentially as expected (testing one node only by design), but the stage_two_tests never run or are queued. If I do "pav wait s####", I see the test_a and test_b status periodically update, but no other tests. Is this a bug or am I doing something incorrectly? Also the python process associated with the series job continues to run long after test_a and test_b have completed. The same problem is seen running under the latest/master tree.
series/compute.yml:
test_sets: stage_one_tests: tests:
test_b stage_two_tests: depends_on: ['stage_one_tests'] depends_pass: True tests:
ordered: True simultaneous: 1 repeat: 1