[issue7805] test_multiprocessing failure

2011-04-04 Thread STINNER Victor
Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue7805] test_multiprocessing failure

2010-03-08 Thread Florent Xicluna
Florent Xicluna added the comment: This last bug is fixed, too. http://bugs.python.org/issue1731717#msg100643 -- status: pending -> closed ___ Python tracker ___

[issue7805] test_multiprocessing failure

2010-03-04 Thread Florent Xicluna
Florent Xicluna added the comment: Sometimes it triggers a different issue, with patch applied (ia64 Ubuntu trunk): test_multiprocessing test test_multiprocessing failed -- Traceback (most recent call last): File "/home/pybot/buildarea/trunk.klose-debian-ia64/build/Lib/test/test_multiprocess

[issue7805] test_multiprocessing failure

2010-03-04 Thread Florent Xicluna
Florent Xicluna added the comment: Thanks Stefan for the analysis. This patch should fix the issue, and make the buildbots happy. -- stage: needs patch -> patch review Added file: http://bugs.python.org/file16429/issue7805_process_is_alive_py3.diff _

[issue7805] test_multiprocessing failure

2010-02-20 Thread Stefan Krah
Stefan Krah added the comment: I found the problem. On a loaded machine, an attempt is made to get the pid of the worker before the process has properly started. There are several places where a sleep could be inserted. Perhaps Process.start() should wait until the child's pid is not None? ---

[issue7805] test_multiprocessing failure

2010-02-12 Thread Antoine Pitrou
Antoine Pitrou added the comment: Indeed, I forgot to mention that the Debian Lenny install I reproduce the bug on is a single core (virtual) machine. -- ___ Python tracker ___

[issue7805] test_multiprocessing failure

2010-02-12 Thread Stefan Krah
Stefan Krah added the comment: I can reproduce it almost always under these conditions: System: Ubuntu Intrepid 64-bit, running on the actual hardware. CPU: Core 2 Duo. Load: At least one core maxed out by another process. On an empty machine I haven't reproduced it yet. -- nosy: +skr

[issue7805] test_multiprocessing failure

2010-02-01 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- versions: +Python 2.6, Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue7805] test_multiprocessing failure

2010-02-01 Thread Antoine Pitrou
Antoine Pitrou added the comment: Also witnessed on one of the buildbots: test test_multiprocessing failed -- Traceback (most recent call last): File "/home/pybot/buildarea/3.x.klose-debian-ia64/build/Lib/test/test_multiprocessing.py", line 1076, in test_pool_worker_lifetime self.assert

[issue7805] test_multiprocessing failure

2010-01-29 Thread Florent Xicluna
Florent Xicluna added the comment: Confirmed. I got a Py3k warning on 2.7 about "unorderable types". -- nosy: +flox versions: +Python 2.7 ___ Python tracker ___

[issue7805] test_multiprocessing failure

2010-01-29 Thread Antoine Pitrou
New submission from Antoine Pitrou : This is a fresh py3k checkout on a fresh Debian Lenny install: == ERROR: test_pool_worker_lifetime (test.test_multiprocessing.WithProcessesTestPoolWorkerLifetime) ---