GeezerVison is showing github.com — gh-146004: propagate all -X options to multiprocessing child processes by gpshead · Pull Request #146005 · python/cpython
Conversation
gpshead
commented
Mar 16, 2026
•
edited by bedevere-app
Bot
Loading
Uh oh!
There was an error while loading. Please reload this page.
See the issue for details. Our list of -X options to opt-in was overlooking a lot. CI and buildbot tests on these may prove interesting.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
Auto-backported test will probably fail CI as the test includes new -X options that older releases don't have. I'll clean that up in the backport PR branches.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
|
Thanks @gpshead for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14.
🐍🍒⛏🤖
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
Sorry, @gpshead, I could not cleanly backport this to 3.13 due to a conflict.
Please backport using cherry_picker on command line.
cherry_picker 1efe441de7c448852b9ba51fb0db4d355a7157a8 3.13
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️
Hi! The buildbot AMD64 Windows Server 2022 NoGIL 3.x (tier-1) has failed when building commit 1efe441.
What do you need to do:
- Don't panic.
- Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
- Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1241/builds/8204) and take a look at the build logs.
- Check if the failure is related to this commit (1efe441) or if it is a false positive.
- If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.
You can take a look at the buildbot page here:
https://buildbot.python.org/#/builders/1241/builds/8204
Summary of the results of the build (if available):
==
Click to see traceback logs
Traceback (most recent call last):
File "C:\bbarea\3.x.itamaro-win64-srv-22-aws.x64.nogil\build\Lib\test\support\os_helper.py", line 524, in temp_dir
os.mkdir(path)
~~~~~~~~^^^^^^
FileExistsError: [WinError 183] Cannot create a file when that file already exists: 'C:\\bbarea\\3.x.itamaro-win64-srv-22-aws.x64.nogil\\build\\build\\test_python_13292æ'
Stack (most recent call last):
File "C:\bbarea\3.x.itamaro-win64-srv-22-aws.x64.nogil\build\Lib\runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "C:\bbarea\3.x.itamaro-win64-srv-22-aws.x64.nogil\build\Lib\runpy.py", line 87, in _run_code
exec(code, run_globals)
File "C:\bbarea\3.x.itamaro-win64-srv-22-aws.x64.nogil\build\Lib\test\libregrtest\worker.py", line 141, in <module>
main()
File "C:\bbarea\3.x.itamaro-win64-srv-22-aws.x64.nogil\build\Lib\test\libregrtest\worker.py", line 136, in main
with os_helper.temp_cwd(work_dir, quiet=True):
File "C:\bbarea\3.x.itamaro-win64-srv-22-aws.x64.nogil\build\Lib\contextlib.py", line 141, in __enter__
return next(self.gen)
File "C:\bbarea\3.x.itamaro-win64-srv-22-aws.x64.nogil\build\Lib\test\support\os_helper.py", line 597, in temp_cwd
with temp_dir(path=name, quiet=quiet) as temp_path:
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️
Hi! The buildbot AMD64 Windows PGO Tailcall 3.x (tier-1) has failed when building commit 1efe441.
What do you need to do:
- Don't panic.
- Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
- Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1870/builds/252) and take a look at the build logs.
- Check if the failure is related to this commit (1efe441) or if it is a false positive.
- If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.
You can take a look at the buildbot page here:
https://buildbot.python.org/#/builders/1870/builds/252
Failed tests:
Summary of the results of the build (if available):
==
Click to see traceback logs
Traceback (most recent call last):
File "C:\bbarea\3.x.itamaro-win64-srv-22-aws.tailcall.pgo\build\Lib\test\test_profiling\test_sampling_profiler\test_advanced.py", line 169, in test_native_frames_enabled
self.assertFalse(any(stack.endswith(";<native>") for stack in stacks))
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: True is not false
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️
Hi! The buildbot AMD64 Windows Server 2022 NoGIL 3.14 (tier-1) has failed when building commit 28d3b9b.
What do you need to do:
- Don't panic.
- Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
- Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1717/builds/1129) and take a look at the build logs.
- Check if the failure is related to this commit (28d3b9b) or if it is a false positive.
- If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.
You can take a look at the buildbot page here:
https://buildbot.python.org/#/builders/1717/builds/1129
Summary of the results of the build (if available):
==
Click to see traceback logs
remote: Enumerating objects: 11, done.
remote: Counting objects: 10% (1/10)
remote: Counting objects: 20% (2/10)
remote: Counting objects: 30% (3/10)
remote: Counting objects: 40% (4/10)
remote: Counting objects: 50% (5/10)
remote: Counting objects: 60% (6/10)
remote: Counting objects: 70% (7/10)
remote: Counting objects: 80% (8/10)
remote: Counting objects: 90% (9/10)
remote: Counting objects: 100% (10/10)
remote: Counting objects: 100% (10/10), done.
remote: Total 11 (delta 9), reused 9 (delta 9), pack-reused 1 (from 1)
From https://github.com/python/cpython
* branch 3.14 -> FETCH_HEAD
Note: switching to '28d3b9bc56df6c2da3e898a0b7a066df5761b04d'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c <new-branch-name>
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
HEAD is now at 28d3b9bc56d [3.14] gh-146004: propagate all -X options to multiprocessing child processes (GH-146005) (#146552)
Switched to and reset branch '3.14'
Could Not Find C:\bbarea\3.14.itamaro-win64-srv-22-aws.x64.nogil\build\Lib\*.pyc
The system cannot find the file specified.
Could Not Find C:\bbarea\3.14.itamaro-win64-srv-22-aws.x64.nogil\build\PCbuild\python*.zip
Could Not Find C:\bbarea\3.14.itamaro-win64-srv-22-aws.x64.nogil\build\PCbuild\python*.zip
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️
Hi! The buildbot AMD64 Windows10 3.x (tier-1) has failed when building commit 1efe441.
What do you need to do:
- Don't panic.
- Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
- Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/146/builds/13440) and take a look at the build logs.
- Check if the failure is related to this commit (1efe441) or if it is a false positive.
- If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.
You can take a look at the buildbot page here:
https://buildbot.python.org/#/builders/146/builds/13440
Summary of the results of the build (if available):
==
Click to see traceback logs
Traceback (most recent call last):
File "D:\buildarea\3.x.bolen-windows10\build\Lib\test\support\os_helper.py", line 524, in temp_dir
os.mkdir(path)
~~~~~~~~^^^^^^
FileExistsError: [WinError 183] Cannot create a file when that file already exists: 'D:\\buildarea\\3.x.bolen-windows10\\build\\build\\test_python_1152æ'
Stack (most recent call last):
File "D:\buildarea\3.x.bolen-windows10\build\Lib\runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "D:\buildarea\3.x.bolen-windows10\build\Lib\runpy.py", line 87, in _run_code
exec(code, run_globals)
File "D:\buildarea\3.x.bolen-windows10\build\Lib\test\libregrtest\worker.py", line 141, in <module>
main()
File "D:\buildarea\3.x.bolen-windows10\build\Lib\test\libregrtest\worker.py", line 136, in main
with os_helper.temp_cwd(work_dir, quiet=True):
File "D:\buildarea\3.x.bolen-windows10\build\Lib\contextlib.py", line 141, in __enter__
return next(self.gen)
File "D:\buildarea\3.x.bolen-windows10\build\Lib\test\support\os_helper.py", line 597, in temp_cwd
with temp_dir(path=name, quiet=quiet) as temp_path:
Traceback (most recent call last):
File "D:\buildarea\3.x.bolen-windows10\build\Lib\test\support\os_helper.py", line 524, in temp_dir
os.mkdir(path)
~~~~~~~~^^^^^^
FileExistsError: [WinError 183] Cannot create a file when that file already exists: 'D:\\buildarea\\3.x.bolen-windows10\\build\\build\\test_python_11832æ'
Stack (most recent call last):
File "D:\buildarea\3.x.bolen-windows10\build\Lib\runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "D:\buildarea\3.x.bolen-windows10\build\Lib\runpy.py", line 87, in _run_code
exec(code, run_globals)
File "D:\buildarea\3.x.bolen-windows10\build\Lib\test\libregrtest\worker.py", line 141, in <module>
main()
File "D:\buildarea\3.x.bolen-windows10\build\Lib\test\libregrtest\worker.py", line 136, in main
with os_helper.temp_cwd(work_dir, quiet=True):
File "D:\buildarea\3.x.bolen-windows10\build\Lib\contextlib.py", line 141, in __enter__
return next(self.gen)
File "D:\buildarea\3.x.bolen-windows10\build\Lib\test\support\os_helper.py", line 597, in temp_cwd
with temp_dir(path=name, quiet=quiet) as temp_path:
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️
Hi! The buildbot AMD64 Windows11 Bigmem 3.x (tier-1) has failed when building commit 1efe441.
What do you need to do:
- Don't panic.
- Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
- Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1079/builds/8289) and take a look at the build logs.
- Check if the failure is related to this commit (1efe441) or if it is a false positive.
- If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.
You can take a look at the buildbot page here:
https://buildbot.python.org/#/builders/1079/builds/8289
Summary of the results of the build (if available):
==
Click to see traceback logs
remote: Enumerating objects: 11, done.
remote: Counting objects: 10% (1/10)
remote: Counting objects: 20% (2/10)
remote: Counting objects: 30% (3/10)
remote: Counting objects: 40% (4/10)
remote: Counting objects: 50% (5/10)
remote: Counting objects: 60% (6/10)
remote: Counting objects: 70% (7/10)
remote: Counting objects: 80% (8/10)
remote: Counting objects: 90% (9/10)
remote: Counting objects: 100% (10/10)
remote: Counting objects: 100% (10/10), done.
remote: Compressing objects: 25% (1/4)
remote: Compressing objects: 50% (2/4)
remote: Compressing objects: 75% (3/4)
remote: Compressing objects: 100% (4/4)
remote: Compressing objects: 100% (4/4), done.
remote: Total 11 (delta 6), reused 6 (delta 6), pack-reused 1 (from 1)
From https://github.com/python/cpython
* branch main -> FETCH_HEAD
Note: switching to '1efe441de7c448852b9ba51fb0db4d355a7157a8'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c <new-branch-name>
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
HEAD is now at 1efe441de7c gh-146004: propagate all -X options to multiprocessing child processes (GH-146005)
Switched to and reset branch 'main'
Could Not Find R:\buildarea\3.x.ambv-bb-win11.bigmem\build\Lib\*.pyc
The system cannot find the file specified.
Could Not Find R:\buildarea\3.x.ambv-bb-win11.bigmem\build\PCbuild\python*.zip
Could Not Find R:\buildarea\3.x.ambv-bb-win11.bigmem\build\PCbuild\python*.zip
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️
Hi! The buildbot AMD64 Windows10 3.14 (tier-1) has failed when building commit 28d3b9b.
What do you need to do:
- Don't panic.
- Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
- Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1711/builds/890) and take a look at the build logs.
- Check if the failure is related to this commit (28d3b9b) or if it is a false positive.
- If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.
You can take a look at the buildbot page here:
https://buildbot.python.org/#/builders/1711/builds/890
Summary of the results of the build (if available):
==
Click to see traceback logs
remote: Enumerating objects: 11, done.
remote: Counting objects: 14% (1/7)
remote: Counting objects: 28% (2/7)
remote: Counting objects: 42% (3/7)
remote: Counting objects: 57% (4/7)
remote: Counting objects: 71% (5/7)
remote: Counting objects: 85% (6/7)
remote: Counting objects: 100% (7/7)
remote: Counting objects: 100% (7/7), done.
remote: Total 11 (delta 7), reused 7 (delta 7), pack-reused 4 (from 2)
From https://github.com/python/cpython
* branch 3.14 -> FETCH_HEAD
Note: switching to '28d3b9bc56df6c2da3e898a0b7a066df5761b04d'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c <new-branch-name>
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
HEAD is now at 28d3b9bc56d [3.14] gh-146004: propagate all -X options to multiprocessing child processes (GH-146005) (#146552)
Switched to and reset branch '3.14'
Could Not Find D:\buildarea\3.14.bolen-windows10\build\Lib\*.pyc
The system cannot find the file specified.
Could Not Find D:\buildarea\3.14.bolen-windows10\build\PCbuild\python*.zip
Could Not Find D:\buildarea\3.14.bolen-windows10\build\PCbuild\python*.zip
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
test_support fails on Windows buildbots:
Warning -- files was modified by test_support
Warning -- Before: []
Warning -- After: ['tmp/']
I don't see the relationship with the change.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️
Hi! The buildbot AMD64 Windows11 Non-Debug 3.14 (tier-1) has failed when building commit 28d3b9b.
What do you need to do:
- Don't panic.
- Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
- Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/1684/builds/511) and take a look at the build logs.
- Check if the failure is related to this commit (28d3b9b) or if it is a false positive.
- If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.
You can take a look at the buildbot page here:
https://buildbot.python.org/#/builders/1684/builds/511
Summary of the results of the build (if available):
==
Click to see traceback logs
remote: Enumerating objects: 16, done.
remote: Counting objects: 12% (1/8)
remote: Counting objects: 25% (2/8)
remote: Counting objects: 37% (3/8)
remote: Counting objects: 50% (4/8)
remote: Counting objects: 62% (5/8)
remote: Counting objects: 75% (6/8)
remote: Counting objects: 87% (7/8)
remote: Counting objects: 100% (8/8)
remote: Counting objects: 100% (8/8), done.
remote: Total 16 (delta 7), reused 7 (delta 7), pack-reused 8 (from 3)
From https://github.com/python/cpython
* branch 3.14 -> FETCH_HEAD
Note: switching to '28d3b9bc56df6c2da3e898a0b7a066df5761b04d'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c <new-branch-name>
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
HEAD is now at 28d3b9bc56d [3.14] gh-146004: propagate all -X options to multiprocessing child processes (GH-146005) (#146552)
Switched to and reset branch '3.14'
Could Not Find b:\uildarea\3.14.ware-win11.nondebug\build\Lib\*.pyc
The system cannot find the file specified.
Could Not Find b:\uildarea\3.14.ware-win11.nondebug\build\PCbuild\python*.zip
Could Not Find b:\uildarea\3.14.ware-win11.nondebug\build\PCbuild\python*.zip
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
picnixz
commented
Mar 28, 2026
•
edited
Loading
Uh oh!
There was an error while loading. Please reload this page.
|
I think the problem is ['-X', 'pycache_prefix=/tmp/pycache']. We should use another temporary folder here.
(The problem is likely because we are using / on Windows platforms)
|
chris-eibl and zware reacted with thumbs up emoji
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
picnixz
commented
Mar 28, 2026
•
edited
Loading
Uh oh!
There was an error while loading. Please reload this page.
|
I suggest just using test.support's temporary directory instead (a fresh one). It doesn't matter that we use a real OS-tempdir
|
chris-eibl and gpshead reacted with thumbs up emoji
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
I won't be able to get to this today. That makes sense as a fix.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
No worries! Chris handled it already: #146580
|
gpshead reacted with heart emoji
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
|
['-X', 'dev'],
|
|
|
['-Wignore', '-X', 'dev'],
|
|
|
['-X', 'cpu_count=4'],
|
|
|
['-X', 'disable-remote-debug'],
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is documented as
with underscores.
Furthermore, -X presite=package.module, -X gil=0,1 and some more aren't listed here.
Not a big issue IMHO, since this just tests that whatever we pass in is returned from args_from_interpreter_flags?
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So an alternative fix for #146580 would be to just remove ['-X', 'pycache_prefix=/tmp/pycache'],?
Sorry, didn't realize earlier, just stumbled over it now ...
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
clin1234
pushed a commit
to clin1234/cpython
that referenced
this pull request
Apr 16, 2026
…ocesses (pythonGH-146005)
Propagate all -X command line options to multiprocessing spawned child Python processes.
ljfp
pushed a commit
to ljfp/cpython
that referenced
this pull request
Apr 25, 2026
…ocesses (pythonGH-146005)
Propagate all -X command line options to multiprocessing spawned child Python processes.
|
Please don't forget about backports.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
hanlee55
added a commit
to hanlee55/cpython
that referenced
this pull request
Aug 17, 2026
…ocesses (pythonGH-146005)
Propagate all -X command line options to multiprocessing spawned child Python processes.
(cherry picked from commit 1efe441)
Co-authored-by: Gregory P. Smith <[email protected]>
Reviewers
vstinner
vstinner approved these changes
Uh oh!
There was an error while loading. Please reload this page.
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
|