Charles-Francois Natali neolo...@free.fr added the comment:
Does this only happen on Cygwin buildbots ?
If yes, then it might simply be an issue with Cygwin's fork implementation,
which is much slower than natively.
Right now, the test waits 0.5s before checking that the processes are started,
Antoine Pitrou pit...@free.fr added the comment:
There is no Cygwin buildbot, this is a regular Windows buildbot (despite the
path in the traceback).
That said, spawning processes is quite slow under Windows anyway (much slower
than under Linux). So we could up the countdown.
--
Roundup Robot devnull@devnull added the comment:
New changeset c4a514199dba by Antoine Pitrou in branch '3.2':
Issue #11766: increase countdown waiting for a pool of processes to start
http://hg.python.org/cpython/rev/c4a514199dba
New changeset 3eac8302a448 by Antoine Pitrou in branch
Roundup Robot devnull@devnull added the comment:
New changeset 2e4cdaffe493 by Antoine Pitrou in branch '2.7':
Issue #11766: increase countdown waiting for a pool of processes to start
http://hg.python.org/cpython/rev/2e4cdaffe493
--
___
Python
Antoine Pitrou pit...@free.fr added the comment:
Hopefully fixed now, thanks for your diagnosis!
--
resolution: - fixed
stage: - committed/rejected
status: open - closed
versions: -Python 3.1
___
Python tracker rep...@bugs.python.org
Changes by STINNER Victor victor.stin...@haypocalc.com:
--
nosy: +haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11766
___
___
New submission from Antoine Pitrou pit...@free.fr:
This sometimes happens on the buildbots:
test test_multiprocessing failed -- Traceback (most recent call last):
File
D:\cygwin\home\db3l\buildarea\3.x.bolen-windows\build\lib\test\test_multiprocessing.py,
line 1191, in
