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 loewis, neologix, python-dev, vstinner
Date 2011-07-04.16:06:39
SpamBayes Score 1.2714861e-05
Marked as misclassified No
Message-id <1309795600.79.0.636488108103.issue12469@psf.upfronthosting.co.za>
In-reply-to
Content
Commits e07b331bf489 and b9de5e55f798 run wakeup and pending signal tests in a subprocess to avoid border effects with threads. It should make these tests more reliable, not only on FreeBSD 6.

PendingSignalsTests now use os.kill() instead of signal.pthread_kill() in most tests (except test_pthread_kill and test_pthread_kill_main_test). We don't need pthread_kill() here anymore because we know that we have exactly one thread. I prefer to use the simple and common os.kill(), and only use pthread_kill in pthread_kill tests.

I'm not proud of that, but I added a workaround for the kernel bug (create a dummy thread, just to initialize the pthread library) in test_pthread_kill(). I don't know how to write a (simple and) reliable test on FreeBSD 6 without this workaround. But I prefer to use a workaround than skipping the test.

I don't think that it would be revelant to use the workaround in test_pthread_kill_main_test(). I chose to skip the test on FreeBSD 6, even if the test was written for this OS (issue #12392).
History
Date User Action Args
2011-07-04 16:06:40vstinnersetrecipients: + vstinner, loewis, neologix, python-dev
2011-07-04 16:06:40vstinnersetmessageid: <1309795600.79.0.636488108103.issue12469@psf.upfronthosting.co.za>
2011-07-04 16:06:40vstinnerlinkissue12469 messages
2011-07-04 16:06:39vstinnercreate