Re: [Zope-dev] zope.testing.runner: protecting against rogue threads

2009-04-05 Thread Dieter Maurer
Christian Theune wrote at 2009-4-3 08:45 +0200: ... I don't want to change the process structure: I only want to assure that the processes we start also quit. Then no objection from me. -- Dieter ___ Zope-Dev maillist - Zope-Dev@zope.org

Re: [Zope-dev] zope.testing.runner: protecting against rogue threads

2009-04-03 Thread Christian Theune
On Thu, 2009-04-02 at 21:17 +0200, Dieter Maurer wrote: Christian Theune wrote at 2009-4-2 13:30 +0200: if tests spawn non-daemon threads, then the test runner can get stuck. The easiest way that I see is to always --exit-with-status and to make --exist-with-status also call sys.exit() when

Re: [Zope-dev] zope.testing.runner: protecting against rogue threads

2009-04-02 Thread Christian Theune
On Thu, 2009-04-02 at 13:30 +0200, Christian Theune wrote: Hi, if tests spawn non-daemon threads, then the test runner can get stuck. The easiest way that I see is to always --exit-with-status and to make --exist-with-status also call sys.exit() when the tests passed. Any objections? I

Re: [Zope-dev] zope.testing.runner: protecting against rogue threads

2009-04-02 Thread Dieter Maurer
Christian Theune wrote at 2009-4-2 13:30 +0200: if tests spawn non-daemon threads, then the test runner can get stuck. The easiest way that I see is to always --exit-with-status and to make --exist-with-status also call sys.exit() when the tests passed. I do not understand the implication. Do

Re: [Zope-dev] zope.testing.runner: protecting against rogue threads

2009-04-02 Thread Marius Gedminas
On Thu, Apr 02, 2009 at 01:30:38PM +0200, Christian Theune wrote: if tests spawn non-daemon threads, then the test runner can get stuck. The easiest way that I see is to always --exit-with-status and to make --exist-with-status also call sys.exit() when the tests passed. Any objections?