[issue18786] test_multiprocessing_spawn crashes under PowerLinux

2013-08-28 Thread Richard Oudkerk
Richard Oudkerk added the comment: It should be fixed now so I will close. -- resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___ __

[issue18786] test_multiprocessing_spawn crashes under PowerLinux

2013-08-28 Thread Charles-François Natali
Charles-François Natali added the comment: > Thanks! You're welcome :) BTW, I don't know if that would fulfill the goal of your test here, but when I want to check for EINTR handling, I just use alarm (see attached patch). The only downside is that the minimum delay is 1 second. -- key

[issue18786] test_multiprocessing_spawn crashes under PowerLinux

2013-08-28 Thread Richard Oudkerk
Richard Oudkerk added the comment: > If the _killer process takes too long to start, it won't send SIGUSR1 > before the p process returns... Thanks! -- ___ Python tracker ___ _

[issue18786] test_multiprocessing_spawn crashes under PowerLinux

2013-08-28 Thread Roundup Robot
Roundup Robot added the comment: New changeset fa23e49c7dd3 by Richard Oudkerk in branch 'default': Issue #18786: Don't reinstall old SIGUSR1 handler prematurely. http://hg.python.org/cpython/rev/fa23e49c7dd3 -- nosy: +python-dev ___ Python tracker <

[issue18786] test_multiprocessing_spawn crashes under PowerLinux

2013-08-28 Thread Charles-François Natali
Charles-François Natali added the comment: > It looks like the main process keeps getting killed by SIGUSR1. > Don't know why. In Lib/test/_test_multiprocessing.py: """ def test_poll_eintr(self): got_signal = [False] def record(*args): got_signal[0] = True

[issue18786] test_multiprocessing_spawn crashes under PowerLinux

2013-08-28 Thread Richard Oudkerk
Richard Oudkerk added the comment: It looks like the main process keeps getting killed by SIGUSR1. Don't know why. -- ___ Python tracker ___

[issue18786] test_multiprocessing_spawn crashes under PowerLinux

2013-08-28 Thread Richard Oudkerk
Richard Oudkerk added the comment: The PPC64 buildbot is still failing intermittently. -- resolution: invalid -> status: closed -> open ___ Python tracker ___ __

[issue18786] test_multiprocessing_spawn crashes under PowerLinux

2013-08-20 Thread Antoine Pitrou
Antoine Pitrou added the comment: Thanks David! The test_gdb failure is another issue (not PowerLinux-specific), see issue18772. -- resolution: -> invalid status: open -> closed ___ Python tracker ___

[issue18786] test_multiprocessing_spawn crashes under PowerLinux

2013-08-20 Thread David Edelsohn
David Edelsohn added the comment: The crash seems to have been due to another user abusing the buildslave system. The remaining failure is a mis-match in the expected GDB output. AssertionError: "{, 'b'}" != "{'b'}" - {, 'b'} + {'b'} -- ___ Python t

[issue18786] test_multiprocessing_spawn crashes under PowerLinux

2013-08-20 Thread David Edelsohn
David Edelsohn added the comment: I am not certain what is going on. Only 3.x appears to be affected, but the problems seem somewhat intermittent. There were some strange processes of another user running on the buildslave, which was driving the load up very high. I have killed the processes a

[issue18786] test_multiprocessing_spawn crashes under PowerLinux

2013-08-19 Thread Antoine Pitrou
New submission from Antoine Pitrou: http://buildbot.python.org/all/builders/PPC64%20PowerLinux%203.x [319/379] test_multiprocessing_spawn /home/shager/cpython-buildarea/3.x.edelsohn-powerlinux-ppc64/build/Lib/multiprocessing/semaphore_tracker.py:121: UserWarning: semaphore_tracker: There appear