| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
After a SIGKILL, the forkserver can no longer report the first child's exit status, so proc.join() returns with exit code 255 while the child may still be running. Wait for the event instead of checking it right after join().
Sorry, something went wrong.
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead. |
Sorry, something went wrong.
|
The ASan failure is unrelated: it is test_sampling_with_collapsed_export in test_profiling, reported as gh-160334. test_multiprocessing_forkserver is skipped under ASan, so this change is not exercised there. |
Sorry, something went wrong.
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead. |
Sorry, something went wrong.
|
Thanks @devdavidejesus for the PR, and @gpshead for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14, 3.15. |
Sorry, something went wrong.
|
GH-160508 is a backport of this pull request to the 3.15 branch. |
Sorry, something went wrong.
|
GH-160509 is a backport of this pull request to the 3.14 branch. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
After the forkserver is killed with SIGKILL, proc.join() returns as soon as the status pipe is closed (exit code 255), possibly before the orphaned child has run. Wait for the event instead of checking it right away.
Test-only change, so no NEWS entry.
Tested with pydebug builds of main:
Fixes #160295.