gh-137638: Use macos-15-intel in GitHub Actions

[JacobCoffee]

• Issue: JIT CI will break with deprecation of x86_64 macOS runners #139153

Fixes #137638

• Issue: [infra][CI] Deal with the sunset of macos-13 @ GHA by Sep 1, 2025 #137638

[savannahostrowski]

Given that GitHub is supporting macOS Intel until Fall 2027, I think we can just bump to the macos-15 runner image instead of using emulation.

[bedevere-app]

A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated.

Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

[hugovk]

Lint error:

.github/workflows/jit.yml:84:21: label "macos-15-intel" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2025", "windows-2022", "windows-2019", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-24.04-arm", "ubuntu-22.04", "ubuntu-22.04-arm", "ubuntu-20.04", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows", "windows-11-arm". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file [runner-label]
   |
84 |             runner: macos-15-intel
   |                     ^~~~~~~~~~~~~~

To fix, add macos-15-intel to:

cpython/.github/actionlint.yaml

Lines 1 to 3 in 872eafd

	self-hosted-runner:
	# Pending https://github.com/rhysd/actionlint/issues/533
	labels: ["windows-11-arm"]

And reference rhysd/actionlint#571.

(It's been fixed in rhysd/actionlint#572 but pending release.)

Please could you also update macos-13 to macos-15-intel in the other workflows?

[savannahostrowski]

LGTM! I'm assuming that you'll update the other actions as part of this PR, so I'll hold off on merging unless you tell me otherwise.

[webknjaz]

@JacobCoffee perhaps link actions/runner-images#13045 or some other announcements in the PR description for context? Looks like GH sent out an email blast about this just a couple hours ago.

[webknjaz]

Maybe update arm runners to 15 in a separate follow-up PR (since this one is declared to be about handling intel)

[hugovk]

Thanks!

[miss-islington-app]

Thanks @JacobCoffee for the PR, and @hugovk for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10, 3.11, 3.12, 3.13, 3.14.
🐍🍒⛏🤖

[miss-islington-app]

Sorry, @JacobCoffee and @hugovk, I could not cleanly backport this to 3.13 due to a conflict.
Please backport using cherry_picker on command line.

cherry_picker 1ae92503647328544866f9586f57eec285e1949a 3.13

[miss-islington-app]

Sorry, @JacobCoffee and @hugovk, I could not cleanly backport this to 3.12 due to a conflict.
Please backport using cherry_picker on command line.

cherry_picker 1ae92503647328544866f9586f57eec285e1949a 3.12

[bedevere-app]

GH-139545 is a backport of this pull request to the 3.14 branch.

[miss-islington-app]

Sorry, @JacobCoffee and @hugovk, I could not cleanly backport this to 3.11 due to a conflict.
Please backport using cherry_picker on command line.

cherry_picker 1ae92503647328544866f9586f57eec285e1949a 3.11

[miss-islington-app]

Sorry, @JacobCoffee and @hugovk, I could not cleanly backport this to 3.10 due to a conflict.
Please backport using cherry_picker on command line.

cherry_picker 1ae92503647328544866f9586f57eec285e1949a 3.10

[bedevere-bot]

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

Hi! The buildbot s390x Fedora Stable Refleaks 3.x (tier-3) has failed when building commit 1ae9250.

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/#/builders/1641/builds/1003) and take a look at the build logs.
4. Check if the failure is related to this commit (1ae9250) 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/1641/builds/1003

Failed tests:

• test.test_os.test_os
• test_socket

Failed subtests:

• test_aead_aes_gcm - test.test_socket.LinuxKernelCryptoAPI.test_aead_aes_gcm
• test_timerfd_interval - test.test_os.test_os.TimerfdTests.test_timerfd_interval

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

==

Click to see traceback logs

Traceback (most recent call last):
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-stable-s390x.refleak/build/Lib/test/test_os/test_os.py", line 3837, in test_timerfd_interval
    self.assertEqual(self.read_count_signaled(fd), count)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 4 != 3


Traceback (most recent call last):
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-stable-s390x.refleak/build/Lib/test/test_socket.py", line 7165, in test_aead_aes_gcm
    op.sendall(plain)
    ~~~~~~~~~~^^^^^^^
OSError: [Errno 22] Invalid argument