New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.6rc1: test_threading hangs on FreeBSD 6.3 i386 #48113
Comments
sources: 2.6rc1 tarball it makes no difference whether test_threading is run as part of make test a log from a verbose run:
task <thread 2> done task <thread 4> done Exception in thread Thread-1:
Traceback (most recent call last):
File "/home/andymac/build/Python-2.6rc1/Lib/threading.py", line 522,
in __bootstrap_inner
self.run()
File "/home/andymac/build/Python-2.6rc1/Lib/threading.py", line 477,
in run
self.__target(*self.__args, **self.__kwargs)
File "<string>", line 14, in worker
OSError: [Errno 4] Interrupted system call Exception KeyboardInterrupt in <module 'threading' from |
I should add that this is a regression of the trunk, as I built and |
I also see this in release25-maint's test_threading This is likely related to the fixes for issue bpo-874900 but i'm not sure (also fyi - I used a premade barebones FreeBSD 6.3 VMWare image from |
and as expected, also happens with py3k. |
fyi the FreeBSD 6.3 libpthread PANIC message comes from the |
attaching a stand alone script to exercise the bug. based on the |
instrumenting Python/thread_pthread.h and turning on thread debugging in I'm inclined to say that this is a FreeBSD 6.3 bug. The What should we do in Python for this? Just disable this unit test on |
I've briefly got a FreeBSD 7.0 amd64 setup available, and test_threading Short term fix I'd suggest is to only disable this part of the test for I also checked my OS/2 EMX build and wasn't surprised to see it fail on If a disabler is added for FreeBSD as above, 'os2emx' should be in the |
test_threading also passes on FreeBSD 7.0 i386. |
I've attached a simple patch which deactivates $ ./python -E -tt Lib/test/regrtest.py test_threading
test_threading
1 test OK.
Unhandled exception in thread started by
Error in sys.excepthook: Original exception was: |
I believe this issue ties into the underlying problem FreeBSD 6.x upto The issue should be fixed in FreeBSD 6.4 (currently in beta), but it |
Cygwin1.5 also hangs on test_3_join_in_forked_from_thread. ====================================================================== Traceback (most recent call last):
File "Lib/test/test_threading.py", line 400, in
test_3_join_in_forked_from_thr
ead
self._run_and_join(script)
File "Lib/test/test_threading.py", line 342, in _run_and_join
self.assertEqual(data, "end of main\nend of thread\n")
AssertionError: '' != 'end of main\nend of thread\n' If stdout is unbuffered mode, |
r66703 in trunk (2.6) applies the test_threading_fbsd6.py.patch modified still needs merging over to 3.0 and possibly 2.5. |
marking release blocker for 3.0, the patch just needs to be merged after |
Apparently this can be merged in py3k. (in [...] |
looks like it already has been merged in py3k. |
Ok, so it's not a release blocker anymore :) |
Backported to 2.5 as r67734. |
Hi, I've committed a fix to FreeBSD-CURRENT for POSIX semaphores this morning. Root cause analysis on the fork-mt issue points towards the rtld and As a workaround, you may wish to try my patches against the FreeBSD port thanks! |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: