Garbage threads hang the testrunner when using subunit output

Bug #589787 reported by Māris Fogels on 2010-06-04
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
High
Māris Fogels
zope.testing
Undecided
Unassigned
zope.testrunner
Undecided
Unassigned

Bug Description

Any tests that leave live thread garbage cause the testrunner to hang when the following conditions are met:

 a) The test is in a layer
 b) The layer is in a subprocess
 c) The testrunner is producing subunit-formatted output (via the --subunit flag)
 d) A test leaves live thread garbage

The child layer's testrunner raises an Exception trying to format the thread garbage, which hangs the child process. The parent layer does not know how to deal with this loss, so it hangs. Here is the traceback from the formatting error: http://pastebin.ubuntu.com/443544/

This bug was observed in zope.testing 3.9.4. Presumably it has been present since subunit output was introduced in 3.9.0.

Related branches

Māris Fogels (mars) on 2010-06-04
Changed in launchpad-foundations:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Māris Fogels (mars)
Māris Fogels (mars) wrote :

This was fixed in Launchpad by landing a patched version of zope.testing 3.9.4, devel/r10956. We can integrate 3.9.7 at a later time.

Changed in launchpad-foundations:
status: In Progress → Fix Committed
Changed in launchpad-foundations:
milestone: none → 10.06
tags: added: qa-needstesting
Māris Fogels (mars) on 2010-06-15
tags: added: qa-untestable
removed: qa-needstesting
Curtis Hovey (sinzui) on 2010-07-07
Changed in launchpad-foundations:
status: Fix Committed → Fix Released
Benji York (benji) on 2010-10-15
Changed in zope.testing:
status: New → Invalid
Changed in zope.testrunner:
status: New → Fix Committed
Marius Gedminas (mgedmin) wrote :

The fix was merged to zope.testrunner prior to the 4.0.0 release, in r117583. For some reason it's not mentioned in the changelog.

Changed in zope.testrunner:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers