[issue3109] test_multiprocessing seems fragile
Antoine Pitrou
report at bugs.python.org
Sat Jun 14 23:15:30 CEST 2008
Antoine Pitrou <pitrou at free.fr> added the comment:
Oh, in another regrtest run, test_multiprocessing just hanged without
eating any CPU, this is what it printed after I pressed Ctrl-C:
test_multiprocessing
Process PoolWorker-5:4:
Traceback (most recent call last):
File "/home/antoine/py3k/traceback/Lib/multiprocessing/process.py",
line 237, in _bootstrap
Process PoolWorker-5:3:
Traceback (most recent call last):
File "/home/antoine/py3k/traceback/Lib/multiprocessing/process.py",
line 237, in _bootstrap
Process PoolWorker-5:2:
Traceback (most recent call last):
File "/home/antoine/py3k/traceback/Lib/multiprocessing/process.py",
line 237, in _bootstrap
Process PoolWorker-5:1:
Traceback (most recent call last):
File "/home/antoine/py3k/traceback/Lib/multiprocessing/process.py",
line 237, in _bootstrap
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue3109>
_______________________________________
More information about the Python-bugs-list
mailing list