This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients martin.panter, python-dev, vstinner
Date 2016-05-30.12:47:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1464612465.66.0.0237232967677.issue22331@psf.upfronthosting.co.za>
In-reply-to
Content
When we talk about signals, we must always be careful of threads. Python unit tests are known (at least by me ;-)) to "leak" threads. IMO the first step to make the test more reliable is to start it in a fresh process to control exactly the number of threads.

A fresh process avoids also to inherit an expected signal and/or signal handler.

I modified test_eintr recently to do something similar.
History
Date User Action Args
2016-05-30 12:47:45vstinnersetrecipients: + vstinner, python-dev, martin.panter
2016-05-30 12:47:45vstinnersetmessageid: <1464612465.66.0.0237232967677.issue22331@psf.upfronthosting.co.za>
2016-05-30 12:47:45vstinnerlinkissue22331 messages
2016-05-30 12:47:45vstinnercreate