testrunner should log currently running test so our test-killer can tell us
Bug #202119 reported by
Christian Reis
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
The test killer that aborts tests that have run for more than a few seconds does so without making sure we can actually know what hung. Perhaps this is caused by buffering of the output. Given it's kicked in in a few instances where we have no idea why it happened (the log output says middle-
Stuart suggests having BaseLayer.testSetup leave a log of what test is running, and having the test killer read that and output it after it's finished its work.
I thought including ps auxww output might be helpful as well.
Revision history for this message
| Francis J. Lacoste (flacoste) wrote | #1 |
| Changed in launchpad: | |
| status: | New → Won't Fix |
Revision history for this message
| Māris Fogels (mars) wrote | #2 |
To post a comment you must log in.
The buffering problem was fixed in the zope testrunner, so this shouldn't be needed anymore.