Richard Oudkerk shibt...@gmail.com added the comment:
I've recently started seeing this failure repeatably on Linux (Ubuntu
Jaunty):
The test is newly enabled. Does repeatably mean you always get the failure?
I have not seen any failures on the Linux buildbots.
--
Vinay Sajip vinay_sa...@yahoo.co.uk added the comment:
Does repeatably mean you always get the failure?
Yes, every time. The first symptom is always a ConnectionRefusedError.
I have not seen any failures on the Linux buildbots.
I'm running a fairly old version of Ubuntu, which might be
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset 3d900c9641c9 by Richard Oudkerk in branch 'default':
Issue #14727: Fix race in test_multiprocessing
http://hg.python.org/cpython/rev/3d900c9641c9
--
nosy: +python-dev
___
Richard Oudkerk shibt...@gmail.com added the comment:
I found a race where a connection attempt could happen before the listening
socket's listen() method was called.
Vinay, could you update and try again please.
--
___
Python tracker
Vinay Sajip vinay_sa...@yahoo.co.uk added the comment:
test_multiprocessing now passes. Thanks for the quick turnaround.
--
assignee: - sbt
resolution: - fixed
stage: - committed/rejected
status: open - closed
___
Python tracker
New submission from Vinay Sajip vinay_sa...@yahoo.co.uk:
I've recently started seeing this failure repeatably on Linux (Ubuntu Jaunty):
[195/364] test_multiprocessing
Process Process-133:
Traceback (most recent call last):
File
Vinay Sajip vinay_sa...@yahoo.co.uk added the comment:
Some more information: after the above-described appears, the test hangs. When
interrupted with a Ctrl+C, this is displayed:
^CProcess PoolWorker-104:
Process PoolWorker-102:
Process PoolWorker-105:1:
Process PoolWorker-101:
Process
