@hugovk can I get a run on the buildbots for this PR?

Certainly!

Let's check if you can do it yourself: either apply one of thetest-with-buildbots ortest-with-refleak-buildbots labels, or add a comment like! buildbot optional-regex (but no space between exclamation mark and buildbot) to run a subset.

🤖 New build scheduled with the buildbot fleet by@graingert for commitc06c3db 🤖

If you want to schedule another build, you need to add the🔨 test-with-buildbots label again.

🤖 New build scheduled with the buildbot fleet by@graingert for commit7123093 🤖

If you want to schedule another build, you need to add the🔨 test-with-buildbots label again.

@hugovk do you know where I can see the status?

You can click the "Details" links in the status checks:

Some of those failing ones were already failing for previous builds, so aren't necessarily caused by this PR.

You can click the "Details" links in the status checks:

Some of those failing ones were already failing for previous builds, so aren't necessarily caused by this PR.

Ah those hadn't shown up yet

The warnings have been fixed in other PRs inmain, and this PR is back to turning future warnings into errors. If there are no objections, I'll merge this later today.

Thanks@graingert for the PR, and@hugovk for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12, 3.13.
🐍🍒⛏🤖 I'm not a witch! I'm not a witch!

Sorry,@graingert and@hugovk, I could not cleanly backport this to3.13 due to a conflict.
Please backport usingcherry_picker on command line.

cherry_picker 8a00c9a4d2ce9d373b13f8f0a2265a65f4523293 3.13

Sorry,@graingert and@hugovk, I could not cleanly backport this to3.12 due to a conflict.
Please backport usingcherry_picker on command line.

cherry_picker 8a00c9a4d2ce9d373b13f8f0a2265a65f4523293 3.12

GH-131802 is a backport of this pull request to the3.13 branch.

⚠️⚠️⚠️ Buildbot failure⚠️⚠️⚠️

Hi! The buildbotaarch64 Fedora Stable LTO 3.x (tier-2) has failed when building commit8a00c9a.

What do you need to do:

1. Don't panic.
2. Checkthe buildbot page in the devguide if you don't know what the buildbots are or how they work.
3. Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/336/builds/6580) and take a look at the build logs.
4. Check if the failure is related to this commit (8a00c9a) or if it is a false positive.
5. 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/336/builds/6580

Summary of the results of the build (if available):

==

Traceback (most recent call last):  File"/home/buildbot/buildarea/3.x.cstratak-fedora-stable-aarch64.lto/build/Lib/threading.py", line1054, in_bootstrap_innerself.run()~~~~~~~~^^  File"/home/buildbot/buildarea/3.x.cstratak-fedora-stable-aarch64.lto/build/Lib/threading.py", line996, inrunself._target(*self._args,**self._kwargs)~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^  File"/home/buildbot/buildarea/3.x.cstratak-fedora-stable-aarch64.lto/build/Lib/test/test_interpreters/test_stress.py", line30, intask    interp= interpreters.create()  File"/home/buildbot/buildarea/3.x.cstratak-fedora-stable-aarch64.lto/build/Lib/test/support/interpreters/__init__.py", line76, increateid= _interpreters.create(reqrefs=True)interpreters.InterpreterError:interpreter creation failedkTraceback (most recent call last):  File"/home/buildbot/buildarea/3.x.cstratak-fedora-stable-aarch64.lto/build/Lib/threading.py", line1054, in_bootstrap_innerself.run()~~~~~~~~^^  File"/home/buildbot/buildarea/3.x.cstratak-fedora-stable-aarch64.lto/build/Lib/threading.py", line996, inrunself._target(*self._args,**self._kwargs)~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^  File"/home/buildbot/buildarea/3.x.cstratak-fedora-stable-aarch64.lto/build/Lib/test/test_interpreters/test_stress.py", line47, inrun    interp= interpreters.create()  File"/home/buildbot/buildarea/3.x.cstratak-fedora-stable-aarch64.lto/build/Lib/test/support/interpreters/__init__.py", line76, increateid= _interpreters.create(reqrefs=True)interpreters.InterpreterError:interpreter creation failedk

the failure is related to this commit, however the code in this PR is working as intended. This has uncovered an issue in subinterpreters:

test_create_many_threaded (test.test_interpreters.test_stress.StressTests.test_create_many_threaded) ...Warning--Uncaughtthreadexception:InterpreterErrorExceptioninthreadThread-166 (task):RuntimeError:FailedtoimportencodingsmoduleDuringhandlingoftheaboveexception,anotherexceptionoccurred:interpreters.InterpreterError:sub-interpretercreationfailedDuringhandlingoftheaboveexception,anotherexceptionoccurred:Traceback (mostrecentcalllast):File"/home/buildbot/buildarea/3.x.cstratak-fedora-stable-aarch64.lto/build/Lib/threading.py",line1054,in_bootstrap_innerself.run()~~~~~~~~^^File"/home/buildbot/buildarea/3.x.cstratak-fedora-stable-aarch64.lto/build/Lib/threading.py",line996,inrunself._target(*self._args,**self._kwargs)~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^File"/home/buildbot/buildarea/3.x.cstratak-fedora-stable-aarch64.lto/build/Lib/test/test_interpreters/test_stress.py",line30,intaskinterp=interpreters.create()File"/home/buildbot/buildarea/3.x.cstratak-fedora-stable-aarch64.lto/build/Lib/test/support/interpreters/__init__.py",line76,increateid=_interpreters.create(reqrefs=True)interpreters.InterpreterError:interpretercreationfailed

That's a known failure, don't worry about it.

Ah you're right it's not a Warning that got raised as an Exception! I panicked like the message said not to

GH-131824 is a backport of this pull request to the3.12 branch.