trial forces the creation of a new threadpool with max size 0 after running a TrialSuite
| Newsgroups | gmane.comp.python.twisted.bugs |
|---|---|
| Message-ID | <[email protected]> |
New submission from exarkun <[email protected]>: `twisted.trial.runner.TrialSuite.run` overrides the base to call `_bail` after doing the normal `run` stuff. The `_bail` method does various Twisted-related cleanup - specifically it fires the shutdown event and waits for all shutdown triggers to complete, and it resizes the reactor threadpool to 0. This resize was introduced in r5030 in order to prevent trial from hanging at the end of the test suite waiting for non-daemon threads to exit (which never would by themselves). This is not necessary now that the reactor cleans up its own threadpool, and it causes problems since by resizing the threadpool to 0, it forces the creation of a ''new'' threadpool if the reactor has already cleaned its up. A size 0 threadpool isn't useful for anything since it can't run any jobs. ---------- Type : defect Component: trial Keywords : Priority : high Nosy : ---------- http://twistedmatrix.com/trac/ticket/3786