Message147293
| Author |
jcea |
| Recipients |
ezio.melotti, jackdied, jcea, neologix, pitrou, terry.reedy, vstinner |
| Date |
2011年11月08日.13:02:40 |
| SpamBayes Score |
0.0002485965 |
| Marked as misclassified |
No |
| Message-id |
<1320757361.84.0.0322344167494.issue11812@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Antoine, the problem with this test is the timeout. We can set an arbitrary timeout, but how big is big enough?.
My change doesn't need a timeout at all. Problem solved.
The only "cosmetic" problem is the risk of "leaking" a thread. But it would not affect the testsuite if it is a daemon thread, and we would only "leak" if the test fails, not under normal circunstances. The complexities suggested are heroic effords trying to manage that thread when simply ignoring it would be acceptable.
I could set a timeout of 5 minutes just to satisfy you, but for that time the test should have been done yet, and the thread collected anyway. I see that more a hack that actually setting the thread to daemon and forget it, knowing that it will automatically die when done. |
|