when selftest is interrupted, it should show the traceback of the interrupted test or better call pdb
Bug #140858 reported by
Martin Pool
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
affects bzr
importance medium
It would be nice if, when selftest is interrupted by ^C, it printed out
any information on tests that had already run: their tracebacks, ideally
also the total number run and a traceback of the test that was
interrupted.
In fact maybe we should just always show the tracebacks immediately when
they occur rather than waiting to the end?
--
Martin Pool
| Changed in bzr: | |
| importance: | Medium → Wishlist |
| status: | New → Triaged |
| Changed in bzr: | |
| status: | Triaged → Confirmed |
Revision history for this message
| Martin Packman (gz) wrote | #1 |
Revision history for this message
| Vincent Ladeuil (vila) wrote | #2 |
| summary: |
- when selftest is interrupted, it should show the results of all tests so - far + when selftest is interrupted, it should show the traceback of the + interrupted test or better call pdb |
| tags: | added: debug selftest |
| tags: | removed: test |
| tags: | added: check-for-breezy |
To post a comment you must log in.
This appears to happen now, modulo the running test interfering with the KeyboardInterrupt exception which is always a risk. Is there any work left to be done in this bug?