testr run --failing when a test runner fails to load tests reports PASSED
Bug #1475975 reported by
Robert Collins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Testrepository |
Triaged
|
Critical
|
Unassigned |
Bug Description
Appears to be tied into the optimisation to not list-tests explicitly.
To post a comment you must log in.
Note that it doesn't lose track of what is failing, which is good, but this is certainly confusing at best.
$ testr run --failing tools/start- container $INSTANCE_PROFILE 1 tools/run- container $INSTANCE_PROFILE 2 /tmp/tmptxYCKM -- ${PYTHON:-python} -m subunit.run discover --load-list /tmp/tmptxYCKM robertc@ lifeless- z140:~/ personal/ testrepository$ testr run --failing tools/start- container $INSTANCE_PROFILE 1 tools/run- container $INSTANCE_PROFILE 2 /tmp/tmpBIzxPf -- ${PYTHON:-python} -m subunit.run discover --load-list /tmp/tmpBIzxPf ======= ======= ======= ======= ======= ======= ======= ======= ======= tests.test_ testcommand. TestTestCommand .test_get_ run_command_ default_ and_list_ expands ------- ------- ------- ------- ------- ------- ------- ------- ------- /tests/ test_testcomman d.py", line 233, in test_get_ run_command_ default_ and_list_ expands
running=
running=
Ran tests in 0.211s (+0.180s)
PASSED (id=6013)
(scratch)
running=
running=
=======
FAIL: testrepository.
tags: worker-0
-------
Traceback (most recent call last):
File "testrepository
('popen', (expected_cmd,),
NameError: global name 'expected_cmd' is not defined
Ran 1 (+1) tests in 0.782s
FAILED (id=6014, failures=1 (+1))