Stefan Krah <stefan-use...@bytereef.org> added the comment: 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/m...@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 ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8712> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
