[issue31510] test_many_processes() of test_multiprocessing_spawn failed on x86-64 Sierra 3.x

2017-10-02 Thread STINNER Victor
Change by STINNER Victor : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue31510] test_many_processes() of test_multiprocessing_spawn failed on x86-64 Sierra 3.x

2017-10-02 Thread STINNER Victor
STINNER Victor added the comment: New changeset e6cfdefa0c2f5bda177e49b228c2c7528f7c239c by Victor Stinner in branch 'master': bpo-31510: Fix multiprocessing test_many_processes() on macOS (#3857)

[issue31510] test_many_processes() of test_multiprocessing_spawn failed on x86-64 Sierra 3.x

2017-10-02 Thread STINNER Victor
STINNER Victor added the comment: Antoine: "It seems other people have similar issues: https://github.com/libuv/libuv/issues/1226 Perhaps we need to relax the test on OSX :-/" Oh thanks for the confirmation. I proposed a patch to accept -SIGKILL on macOS: PR 3857.

[issue31510] test_many_processes() of test_multiprocessing_spawn failed on x86-64 Sierra 3.x

2017-10-02 Thread STINNER Victor
Change by STINNER Victor : -- keywords: +patch pull_requests: +3837 stage: -> patch review ___ Python tracker ___

[issue31510] test_many_processes() of test_multiprocessing_spawn failed on x86-64 Sierra 3.x

2017-10-02 Thread Antoine Pitrou
Antoine Pitrou added the comment: It seems other people have similar issues: https://github.com/libuv/libuv/issues/1226 Perhaps we need to relax the test on OSX :-/ -- ___ Python tracker

[issue31510] test_many_processes() of test_multiprocessing_spawn failed on x86-64 Sierra 3.x

2017-10-02 Thread Antoine Pitrou
Antoine Pitrou added the comment: > It looks like a weak synchronization. It is. I don't remember exactly why I had to add this, I can't reproduce any issue without it anymore... > the signal is sent before Python registered signal handlers? Python signal handlers are not

[issue31510] test_many_processes() of test_multiprocessing_spawn failed on x86-64 Sierra 3.x

2017-09-21 Thread STINNER Victor
STINNER Victor added the comment: test_many_processes() is made in two steps. The bug occurs at the second step which calls proc.terminate() on processes. Code of the test: @classmethod def _sleep_some(cls): time.sleep(100) @classmethod def _test_sleep(cls, delay):

[issue31510] test_many_processes() of test_multiprocessing_spawn failed on x86-64 Sierra 3.x

2017-09-21 Thread STINNER Victor
Changes by STINNER Victor : -- nosy: +pitrou ___ Python tracker ___ ___

[issue31510] test_many_processes() of test_multiprocessing_spawn failed on x86-64 Sierra 3.x

2017-09-21 Thread STINNER Victor
STINNER Victor added the comment: test_many_processes() test was added by Antoine Pitrou in bpo-30589. This test was mentionned in bpo-30703. -- ___ Python tracker

[issue31510] test_many_processes() of test_multiprocessing_spawn failed on x86-64 Sierra 3.x

2017-09-19 Thread STINNER Victor
STINNER Victor added the comment: I failed to reproduce the bug on Linux. -- ___ Python tracker ___ ___

[issue31510] test_many_processes() of test_multiprocessing_spawn failed on x86-64 Sierra 3.x

2017-09-18 Thread STINNER Victor
New submission from STINNER Victor: The process was killed (SIGKILL). See also bpo-30356. http://buildbot.python.org/all/builders/x86-64%20Sierra%203.x/builds/765/steps/test/logs/stdio == FAIL: test_many_processes