[issue31463] test_multiprocessing_fork hangs test_subprocess

2018-06-27 Thread STINNER Victor
STINNER Victor added the comment: > This hangs reliably for me on master: > $ ./python -m test.regrtest test_multiprocessing_fork test_subprocess FYI right now, this command doesn't hang anymore. > ValueError: signal number 32 out of range This bug has been fixed by bpo-2. > Let's take

[issue31463] test_multiprocessing_fork hangs test_subprocess

2018-06-20 Thread STINNER Victor
STINNER Victor added the comment: Antoine: "Let's take another look at the issue: why does test_subprocess need to know about all child processes, rather than those that were launched during test_subprocess?" It seems like this bug has been fixed by bpo-31178, commit

[issue31463] test_multiprocessing_fork hangs test_subprocess

2018-06-20 Thread STINNER Victor
STINNER Victor added the comment: Another old (now fixed) issue of test_subprocess: bpo-31173 "test_subprocess: test_child_terminated_in_stopped_state() leaks a zombie process". -- ___ Python tracker

[issue31463] test_multiprocessing_fork hangs test_subprocess

2018-06-20 Thread STINNER Victor
STINNER Victor added the comment: See also the now hopefully fixed bpo-31509 "test_subprocess hangs randomly on AMD64 Windows10 3.x". -- ___ Python tracker ___

[issue31463] test_multiprocessing_fork hangs test_subprocess

2018-06-20 Thread Pablo Galindo Salgado
Pablo Galindo Salgado added the comment: I would like to work on this issue -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue31463] test_multiprocessing_fork hangs test_subprocess

2018-06-20 Thread STINNER Victor
STINNER Victor added the comment: Last time I was bitten by waitpid(): commit 11045c9d8a21dd9bd182a3939189db02815f9783 Author: Victor Stinner Date: Thu Oct 5 06:32:53 2017 -0700 bpo-31178: Mock os.waitpid() in test_subprocess (#3896) Fix test_exception_errpipe_bad_data() and

[issue31463] test_multiprocessing_fork hangs test_subprocess

2018-06-20 Thread Pablo Galindo Salgado
Change by Pablo Galindo Salgado : -- assignee: -> pablogsal nosy: +pablogsal ___ Python tracker ___ ___ Python-bugs-list mailing

[issue31463] test_multiprocessing_fork hangs test_subprocess

2018-05-23 Thread Antoine Pitrou
Antoine Pitrou added the comment: Let's take another look at the issue: why does test_subprocess need to know about all child processes, rather than those that were launched during test_subprocess? -- ___ Python tracker

[issue31463] test_multiprocessing_fork hangs test_subprocess

2018-05-23 Thread STINNER Victor
STINNER Victor added the comment: > It looks like test_multiprocessing_fork doesn't clean up some of its > subprocesses and then test_subprocess hangs on waitpid(0) forever. Oh strange. This issue was supposed to be fixed. I spent a lot of time to fix such bug, but also

[issue31463] test_multiprocessing_fork hangs test_subprocess

2018-05-03 Thread STINNER Victor
Change by STINNER Victor : -- nosy: +vstinner ___ Python tracker ___ ___

[issue31463] test_multiprocessing_fork hangs test_subprocess

2018-04-22 Thread Miro Hrončok
Miro Hrončok added the comment: > Could you report the signal number issue separately? Thank you! https://bugs.python.org/issue33329 Resetting the Versions back. -- versions: -Python 3.4, Python 3.5, Python 3.6 ___ Python

[issue31463] test_multiprocessing_fork hangs test_subprocess

2018-04-21 Thread Antoine Pitrou
Antoine Pitrou added the comment: There's a test that deliberately kills the semaphore tracker, so that warning should be expected (I don't see it myself, but that might be because of differing warning settings). -- ___ Python

[issue31463] test_multiprocessing_fork hangs test_subprocess

2018-04-21 Thread Benjamin Peterson
Benjamin Peterson added the comment: It doesn't hang for me anymore, but does print this warning: 0:00:00 load avg: 1.59 [1/2] test_multiprocessing_fork Lib/multiprocessing/semaphore_tracker.py:55: UserWarning: semaphore_tracker: process died unexpectedly, relaunching.

[issue31463] test_multiprocessing_fork hangs test_subprocess

2018-04-21 Thread Antoine Pitrou
Antoine Pitrou added the comment: @Benjamin I can't reproduce here. It's true that test_multiprocessing_fork leaves two processes being itself, but that doesn't seem to disturb test_subprocess. @Miro Could you report the signal number issue separately? Thank you!

[issue31463] test_multiprocessing_fork hangs test_subprocess

2018-04-19 Thread Miro Hrončok
Miro Hrončok added the comment: Sorry, I've pressed the button before finishing the thought. ...so this might or might not be relevant to what you observe with master and originally reported. -- ___ Python tracker

[issue31463] test_multiprocessing_fork hangs test_subprocess

2018-04-19 Thread Miro Hrončok
Miro Hrončok added the comment: This started to bother us in Fedora for various Python versions, so chances are something changed on the system level. However for us it seams test_multiprocessing_fork hangs by itself, so this might or might not be relevant to # python3.7

[issue31463] test_multiprocessing_fork hangs test_subprocess

2017-09-14 Thread Benjamin Peterson
New submission from Benjamin Peterson: This hangs reliably for me on master: $ ./python -m test.regrtest test_multiprocessing_fork test_subprocess It looks like test_multiprocessing_fork doesn't clean up some of its subprocesses and then test_subprocess hangs on waitpid(0) forever.