[issue8432] buildbot: test_send_signal of test_subprocess failure

Changes by Antoine Pitrou : -- status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue8432] buildbot: test_send_signal of test_subprocess failure

Antoine Pitrou added the comment: test_subprocess now succeeds on all 3.x buildbots. Will backport and then close. -- resolution: -> fixed status: open -> pending ___ Python tracker ___

[issue8432] buildbot: test_send_signal of test_subprocess failure

Antoine Pitrou added the comment: The fix succeeded on the "sparc Debian 3.x" buildbot while test_subprocess had been failing consistently before. -- ___ Python tracker ___

[issue8432] buildbot: test_send_signal of test_subprocess failure

Antoine Pitrou added the comment: The test fails mostly on very slow machines (not only BSD ones, but also the Debian sparc buildbot). Therefore, I've attempted a fix in r84910 by relaxing timings, and simply skipping the test if it seems we couldn't send the signal in time. -- _

[issue8432] buildbot: test_send_signal of test_subprocess failure

Florent Xicluna added the comment: Also occurs on Python 2.7, with "x86 FreeBSD 7.2" buildbot. (I found it on many builds since revision 83725 at least. Older builds are not available) Seen on "x86 FreeBSD" buildbot, too. test test_subprocess failed -- Traceback (most recent call last): Fil

[issue8432] buildbot: test_send_signal of test_subprocess failure

Stefan Krah added the comment: Issue 8714 could be related as well: On OpenBSD, after a KeyboardInterrupt one has to hit before the traceback appears. This was introduced in (or exposed by) r68460. When Python is compiled without threads, the bug does not occur. -- nosy: +skrah _

[issue8432] buildbot: test_send_signal of test_subprocess failure

STINNER Victor added the comment: > These tests exist and pass on 2.7 and 3.1. Ok. In r78946, for the pure Python implementation, I only see the restoration of the signals which can be related to this issue. -- ___ Python tracker

[issue8432] buildbot: test_send_signal of test_subprocess failure

Antoine Pitrou added the comment: > The problem is maybe that the SIGINT is ignored on these particular > platforms (FreeBSD and Mac OS X). I worked on this topic recently (see > issue #3137) and I cannot guarantee that exceptions are still ignored > somewhere. I can investigate if you give me a

[issue8432] buildbot: test_send_signal of test_subprocess failure

STINNER Victor added the comment: http://www.python.org/dev/buildbot/builders/x86%20FreeBSD%203.x/builds/492 On this report, both implementations (Python and C) failed: FAIL: test_send_signal (test.test_subprocess.POSIXProcessTestCase) FAIL: test_send_signal (test.test_subprocess.ProcessTestCa

[issue8432] buildbot: test_send_signal of test_subprocess failure

Antoine Pitrou added the comment: Since it only happens on 3.x, a possible culprit is “[svn r78946] Replaces the internals of the subprocess module from fork through exec on POSIX systems with a C extension module”. NB: recent URL of deterministic failure under FreeBSD 6.4: http://www.python.o

[issue8432] buildbot: test_send_signal of test_subprocess failure

Michael Foord added the comment: I get this same failure on Mac OS X 10.6.3 as well. -- nosy: +michael.foord ___ Python tracker ___ __

[issue8432] buildbot: test_send_signal of test_subprocess failure

Changes by STINNER Victor : -- title: build: test_send_signal of test_subprocess failure -> buildbot: test_send_signal of test_subprocess failure ___ Python tracker ___ _