[issue30589] With forkserver, Process.exitcode does not get signal number

Antoine Pitrou added the comment: In the end, I'm glad I added a stress test (test_many_processes) as part of this issue. It helper uncover a serious reliability issues in CPython's delivery of signals (https://bugs.python.org/issue30703) and then triggered the discovery of a more minor bug

[issue30589] With forkserver, Process.exitcode does not get signal number

Antoine Pitrou added the comment: I've merged a fix for Python 3.7. Since the fix is a bit delicate, I don't want to risk regression by merging it into 3.6 and 3.5. Closing now. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: -Python 3.5,

[issue30589] With forkserver, Process.exitcode does not get signal number

Antoine Pitrou added the comment: New changeset dfd5f34634f9c505945e9348b4b799544680a7cf by Antoine Pitrou in branch 'master': Fix bpo-30589: improve Process.exitcode with forkserver (#1989) https://github.com/python/cpython/commit/dfd5f34634f9c505945e9348b4b799544680a7cf --

[issue30589] With forkserver, Process.exitcode does not get signal number

Changes by Antoine Pitrou : -- pull_requests: +2055 ___ Python tracker ___ ___

[issue30589] With forkserver, Process.exitcode does not get signal number

Changes by Antoine Pitrou : -- stage: -> patch review ___ Python tracker ___ ___

[issue30589] With forkserver, Process.exitcode does not get signal number

New submission from Antoine Pitrou: The documentation for multiprocessing.exitcode says: """ The child’s exit code. This will be None if the process has not yet terminated. A negative value -N indicates that the child was terminated by signal N. """ This is true for the "fork" method, but