Repository navigation
[3.15] gh-155717: use spawn as the default start method for read-only filesystems (GH-155827) - #155887
[3.15] gh-155717: use spawn as the default start method for read-only filesystems (GH-155827)#155887serhiy-storchaka merged 2 commits into
Conversation
Sorry, something went wrong.
…y filesystems (pythonGH-155827) The "forkserver" start method (the default start method on non-Windows systems) requires the ability to write temporary files, which is not possible if TMPDIR is read-only (e.g., k8s containers mounted with `readOnlyRootFilesystem=True`). On such filesystems, the default start method changes from "forkserver" to "spawn". (cherry picked from commit c144799) Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
|
!buildbot root |
Sorry, something went wrong.
|
🤖 New build scheduled with the buildbot fleet by @picnixz for commit ce0ab72 🤖 Results will be shown at: https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F155887%2Fmerge The command will test the builders whose names match following regular expression: root The builders matched are:
|
Sorry, something went wrong.
|
@picnixz Remember to get peer review: https://discuss.python.org/t/the-3-15-branch-is-locked-for-rc1/108389 |
Sorry, something went wrong.
|
@hugovk I thought automated backports were fine? |
Sorry, something went wrong.
|
this can wait for 3.15.1 |
Sorry, something went wrong.
The "forkserver" start method (the default start method on non-Windows systems)
requires the ability to write temporary files, which is not possible if TMPDIR
is read-only (e.g., k8s containers mounted with readOnlyRootFilesystem=True).
On such filesystems, the default start method changes from "forkserver" to "spawn".
(cherry picked from commit c144799)
Co-authored-by: Bénédikt Tran 10796600+picnixz@users.noreply.github.com