failures are not easily visible in pqm make check error output
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
PQM |
Confirmed
|
High
|
Unassigned |
Bug Description
pqm failures messages, which I think are the result of 'make check', start out with a lot of output about skipped tests. This is really not helpful: I want to know about the actual failures. There are subunit files if more information is needed.
example:
bzr selftest: /home/pqm/
/home/
bzr-2.1.3dev python-2.6.5 Linux-2.
blackbox.
Text attachment: reason
------------
dpush does not handle --revision
------------
blackbox.
Text attachment: reason
------------
dpush does not handle --revision
------------
blackbox.
Text attachment: reason
------------
dpush does not handle --revision
------------
....
Changed in bzr: | |
importance: | Medium → High |
affects: | bzr → pqm |
Changed in pqm: | |
status: | In Progress → Confirmed |
assignee: | Martin Pool (mbp) → nobody |
The simplest way to fix this would be to just change 'make check' back out of using subunit output.
Pros:
* the failure email will be more concise
* the subunit stream seems reasonably often not to be able to be parsed by subunit so it's not reliably useful
* other people running make check will not be surprised by reams of output
* this will avoid some complexity about checking the output that's sometimes caused pqm to fail open
Cons:
* perhaps people do like subunit? (I like the idea in general but I don't find it very useful with pqm).
* changing it might break something in pqm