Cryptic error from subunit when an import fails
Bug #1271133 reported by
Julien Danjou
This bug affects 20 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Testrepository |
Fix Released
|
High
|
Robert Collins | ||
testtools |
Invalid
|
High
|
Unassigned |
Bug Description
When one of the test module fails to import for whatever reason, the raw subunit stream is output by "setup.py testr", something like:
unning testr
running=
Non-zero exit code (2) from test listing. stdout=
[...]
ume.test_
error: testr failed (3)
Which is not user friendly at all.
Changed in testrepository: | |
status: | In Progress → Fix Committed |
assignee: | Alexei Kornienko (alexei-kornienko) → Robert Collins (lifeless) |
Changed in testtools: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in testrepository: | |
importance: | Undecided → High |
Changed in testrepository: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
We need to patch 3 projects to fix this issue: /code.launchpad .net/~alexei- kornienko/ subunit/ bug-1271133 /code.launchpad .net/~alexei- kornienko/ testrepository/ bug-1271133 /github. com/testing- cabal/testtools /pull/77
https:/
https:/
https:/