[issue22331] test_io.test_interrupted_write_text() hangs on the buildbot FreeBSD 7.2

STINNER Victor added the comment: Hum, the resolution is already set to Fixed, and I didn't see this bug last months on buildbots, so I consider that yes, it's fixed. Sorry Martin, I lost track of this issue and so I don't know what to do with your patch :-/ I will just close the issue. -

[issue22331] test_io.test_interrupted_write_text() hangs on the buildbot FreeBSD 7.2

Martin Panter added the comment: Here is a patch with my suggestion to send the signal only when read() returns, and also closing the read end of the pipe before the write end. -- keywords: +patch stage: -> patch review Added file: http://bugs.python.org/file43147/int-write.patch

[issue22331] test_io.test_interrupted_write_text() hangs on the buildbot FreeBSD 7.2

Martin Panter added the comment: Found the same hang on the 3.6 branch, which was definitely running separate processes: http://buildbot.python.org/all/builders/AMD64%20FreeBSD%209.x%203.x/builds/4210/steps/test/logs/stdio == CPython 3.6.0a0 (default:ed6345cb08ab, Apr 29 2016, 18:35:36) [GCC 4.

[issue22331] test_io.test_interrupted_write_text() hangs on the buildbot FreeBSD 7.2

Martin Panter added the comment: Thanks, that is a very good point about threads. I remember that testing tkinter leaves an internal TK or TCL thread running in the background. And I understand Free BSD delivers process signals to arbitrary threads (not necessarily the main thread). But the F

[issue22331] test_io.test_interrupted_write_text() hangs on the buildbot FreeBSD 7.2

STINNER Victor added the comment: I also modified Python 3.6 to run each test file in a fresh process to avoid leaking too much things between tests, to isolate them better. -- ___ Python tracker _

[issue22331] test_io.test_interrupted_write_text() hangs on the buildbot FreeBSD 7.2

STINNER Victor added the comment: When we talk about signals, we must always be careful of threads. Python unit tests are known (at least by me ;-)) to "leak" threads. IMO the first step to make the test more reliable is to start it in a fresh process to control exactly the number of threads.

[issue22331] test_io.test_interrupted_write_text() hangs on the buildbot FreeBSD 7.2

Martin Panter added the comment: This recently hung AMD64 FreeBSD 9.x 3.5. The stack trace was different, and there is only one thread: http://buildbot.python.org/all/builders/AMD64%20FreeBSD%209.x%203.5/builds/828/steps/test/logs/stdio [398/398] test_io Timeout (0:15:00)! Thread 0x00080180

[issue22331] test_io.test_interrupted_write_text() hangs on the buildbot FreeBSD 7.2

STINNER Victor added the comment: The test now pass on the buildbot FreeBSD 7.2. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue22331] test_io.test_interrupted_write_text() hangs on the buildbot FreeBSD 7.2

Roundup Robot added the comment: New changeset baa372eb731c by Victor Stinner in branch '3.4': Issue #22331: Skip test_interrupted_write_text() on FreeBSD older than 8.0 http://hg.python.org/cpython/rev/baa372eb731c New changeset 340d48347295 by Victor Stinner in branch 'default': (Merge 3.4) Is

[issue22331] test_io.test_interrupted_write_text() hangs on the buildbot FreeBSD 7.2

New submission from STINNER Victor: http://buildbot.python.org/all/builders/x86%20FreeBSD%207.2%203.4/builds/332/steps/test/logs/stdio Log: --- [157/389/1] test_io Timeout (1:00:00)! Thread 0x2a4f0790 (most recent call first): File "/usr/home/db3l/buildarea/3.4.bolen-freebsd7/build/Lib/test/te