🤖 New build scheduled with the buildbot fleet by @encukou for commit 78ae2ba 🤖

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

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

Hi! The buildbot s390x SLES 3.x has failed when building commit 664e96a.

What do you need to do:

1. Don't panic.
2. Check the 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/all/#builders/540/builds/3379) and take a look at the build logs.
4. Check if the failure is related to this commit (664e96a) 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/all/#builders/540/builds/3379

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

== Tests result: ENV CHANGED ==

421 tests OK.

10 slowest tests:

• test_concurrent_futures: 2 min 33 sec
• test_multiprocessing_spawn: 2 min 6 sec
• test_tools: 2 min 3 sec
• test_multiprocessing_forkserver: 1 min 16 sec
• test_asyncio: 1 min 13 sec
• test_capi: 1 min 8 sec
• test_signal: 1 min 8 sec
• test_multiprocessing_fork: 1 min 7 sec
• test_tokenize: 50.6 sec
• test_gdb: 46.2 sec

1 test altered the execution environment:
test_import

14 tests skipped:
test_devpoll test_ioctl test_kqueue test_launcher test_msilib
test_nis test_startfile test_tix test_tkinter test_ttk
test_winconsoleio test_winreg test_winsound test_zipfile64

Total duration: 6 min 27 sec

That failure looks unrelated.

The buildbot's next job passed: https://buildbot.python.org/all/#/builders/540/builds/3380

@encukou, it seems that this PR introduced two unused vars:

I'm seeing warnings about it in https://github.com/python/cpython/pull/95874/files:

Thanks for the catch! The warnings will be fixed in #95992