➜

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 skrah
Recipients djmdjm, exarkun, henry.precheur, mark.dickinson, pitrou, skrah
Date 2010-05-15.11:10:28
SpamBayes Score 7.044433e-05
Marked as misclassified No
Message-id <1273921831.57.0.828421115527.issue8712@psf.upfronthosting.co.za>
In-reply-to
Content 
I can't pinpoint the exact causes for each individual test failure. I assumed that they are caused by threading/signal issues, because the tests pass when Python is compiled --without-threads.


But here's a list of possible culprits for future reference:

[pthread's execve(2) breaks close(2)]
http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yes&numbers=6183

[SIGCHLD handler is called at bad timing when linked to libpthread]
http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yes&numbers=6273

[pthread: 100% CPU usage after execv]
http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yes&numbers=6376

[pthread: file descriptors are "pseudo-blocking"]
http://www.mail-archive.com/misc@openbsd.org/msg80643.html

[test_siginterrupt_off broken by libpthread's internal hooking of signals]
[test_itimer_prof broken by libpthread's internal use of SIGPROF]
http://www.openbsd.org/cgi-bin/cvsweb/ports/lang/python/2.6/patches/patch-Lib_test_test_signal_py
History
Date User Action Args
2010-05-15 11:10:31skrahsetrecipients: + skrah, exarkun, mark.dickinson, pitrou, djmdjm, henry.precheur
2010-05-15 11:10:31skrahsetmessageid: <1273921831.57.0.828421115527.issue8712@psf.upfronthosting.co.za>
2010-05-15 11:10:29skrahlinkissue8712 messages
2010-05-15 11:10:28skrahcreate