[issue8712] Skip libpthread related test failures on OpenBSD

Stefan Krah added the comment: All threading issues are fixed in OpenBSD 5.2. -- resolution: -> out of date stage: patch review -> committed/rejected status: open -> closed ___ Python tracker __

[issue8712] Skip libpthread related test failures on OpenBSD

Stefan Krah added the comment: The gentoo-3.x buildbot also shows the threading problems again: test test_subprocess failed -- Traceback (most recent call last): File "/home/buildslave/python-trunk/3.x.norwitz-x86/build/Lib/test/test_subprocess.py", line 770, in test_send_signal self.as

[issue8712] Skip libpthread related test failures on OpenBSD

Stefan Krah added the comment: The FreeBSD-6.4-RELEASE-i386 buildbot has similar libpthread issues. This is just in: == FAIL: test_send_signal (test.test_subprocess.POSIXProcessTestCase) ---

[issue8712] Skip libpthread related test failures on OpenBSD

Stefan Krah 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: [pthre

[issue8712] Skip libpthread related test failures on OpenBSD

Jean-Paul Calderone added the comment: In addition to skipping the tests, would it also make sense to document these known limitations of Python threading on OpenBSD somewhere that end users might see it? -- ___ Python tracker

[issue8712] Skip libpthread related test failures on OpenBSD

Antoine Pitrou added the comment: This looks reasonable. Perhaps you should add a reference to the relevant OpenBSD bug number(s) or URL(s), if any. -- nosy: +exarkun, mark.dickinson, pitrou ___ Python tracker ___

[issue8712] Skip libpthread related test failures on OpenBSD

New submission from Stefan Krah : [Added OpenBSD Python port maintainers to the nosy list.] I've identified a number of tests that all pass when Python is compiled without threads, but fail otherwise. The failures are probably caused by libpthread issues in OpenBSD, as described in this patch: