Changes by STINNER Victor victor.stin...@gmail.com:
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20114
___
Changes by Stefan Krah stefan-use...@bytereef.org:
--
nosy: -skrah
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20114
___
___
Python-bugs-list
STINNER Victor added the comment:
It is probably harmless then.
It makes the buildbot red :-( I would like to see green buildbots :-)
Similar failure on the buildbot SPARC Solaris 10 OpenCSW 3.x. A build takes
between 9 and 10 hours on this buildbot.
Roundup Robot added the comment:
New changeset 5057eaff9d68 by Richard Oudkerk in branch 'default':
Issue #20114: Double timeout in test_semaphore_tracker() to reduce
http://hg.python.org/cpython/rev/5057eaff9d68
--
nosy: +python-dev
___
Python
Richard Oudkerk added the comment:
It is probably harmless then.
I don't think increasing the timeout is necessary -- the multiprocessing tests
already take a long time.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20114
New submission from STINNER Victor:
http://buildbot.python.org/all/builders/AMD64%20FreeBSD%209.0%203.x/builds/6085/steps/test/logs/stdio
==
FAIL: test_semaphore_tracker
Richard Oudkerk added the comment:
How often has this happened?
If the machine was very loaded then maybe the timeout was not enough time for
the semaphore to be cleaned up by the tracker process. But I would expect 1
second to be more than ample.
--
Stefan Krah added the comment:
The machine has a high load: 6 processes at 100% CPU, one of which is
the FreeBSD virtual machine.
--
nosy: +skrah
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20114
