◐ Shell
reader mode source ↗
Skip to content

gh-140189: Use macos-14 runner for iOS CI tests#142444

Merged
freakboy3742 merged 2 commits into
python:mainfrom
freakboy3742:ios-macos-runner
Dec 9, 2025
Merged

gh-140189: Use macos-14 runner for iOS CI tests#142444
freakboy3742 merged 2 commits into
python:mainfrom
freakboy3742:ios-macos-runner

Conversation

@freakboy3742

@freakboy3742 freakboy3742 commented Dec 9, 2025 •
edited by bedevere-app Bot
Loading

Copy link
Copy Markdown
Contributor

We're currently seeing a 2-4% failure rate in iOS tests.

This appears to be caused by a problem with the GitHub Actions macos-15 environment; this environment has been having performance issues since August (see actions/runner-images#12777).

This PR reverts to the macos-14 runner, which apparently isn't subject to the issues the macos-15 runner is experiencing. This means we'll be running iOS tests on an older iOS release (Xcode 15.4, iOS 17.5); but since we're compiling with iOS 13 compatibility, this shouldn't impact anything.

@freakboy3742 freakboy3742 added the needs backport to 3.14 bugs and security fixes label Dec 9, 2025
@bedevere-app bedevere-app Bot mentioned this pull request Dec 9, 2025
Closed
4 tasks
@freakboy3742

freakboy3742 commented Dec 9, 2025

Copy link
Copy Markdown
Contributor Author

@hugovk I've run the iOS tests 6 times today, and it's passed every time; that's not proof that the "missing simulator" problem is fixed, but it's about as good as we're going to get.

As a bonus, it seems to be significantly faster than the macos-15 runner as well (consistently <21 mins, from the look of it).

hugovk
hugovk approved these changes Dec 9, 2025
View reviewed changes

@hugovk hugovk left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hide comment

And revert #142365, or give this a few days to check reliability?

@hugovk hugovk added the infra CI, GitHub Actions, buildbots, Dependabot, etc. label Dec 9, 2025
@mhsmith

mhsmith commented Dec 9, 2025

Copy link
Copy Markdown
Member

I'd say give it a few days, just in case.

Hide details View details @freakboy3742 freakboy3742 merged commit 9188483 into python:main Dec 9, 2025
235 checks passed
@freakboy3742 freakboy3742 deleted the ios-macos-runner branch December 9, 2025 21:52
@miss-islington-app

miss-islington-app Bot commented Dec 9, 2025

Copy link
Copy Markdown

Thanks @freakboy3742 for the PR 🌮🎉.. I'm working now to backport this PR to: 3.14.
🐍🍒⛏🤖

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Dec 9, 2025
@freakboy3742 @miss-islington
pythongh-140189: Use macos-14 runner for iOS CI tests (pythonGH-142444) …
9d0286d 
Switch to the macos-14 runner for iOS CI, working around some instability
in the macos-15 runner.
(cherry picked from commit 9188483)

Co-authored-by: Russell Keith-Magee <russell@keith-magee.com>
@bedevere-app

bedevere-app Bot commented Dec 9, 2025

Copy link
Copy Markdown

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

@bedevere-app bedevere-app Bot removed the needs backport to 3.14 bugs and security fixes label Dec 9, 2025
freakboy3742 added a commit that referenced this pull request Dec 9, 2025
@miss-islington @freakboy3742
[3.14] gh-140189: Use macos-14 runner for iOS CI tests (GH-142444) (#… …
1e495c2 
…142494)

Switch to the macos-14 runner for iOS CI, working around some instability
in the macos-15 runner.
(cherry picked from commit 9188483)

Co-authored-by: Russell Keith-Magee <russell@keith-magee.com>
@bedevere-bot

bedevere-bot commented Dec 9, 2025

Copy link
Copy Markdown

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

Hi! The buildbot AMD64 FreeBSD Refleaks 3.x (tier-3) has failed when building commit 9188483.

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/1613/builds/2486) and take a look at the build logs.
  4. Check if the failure is related to this commit (9188483) 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/1613/builds/2486

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

==

Click to see traceback logs 
Traceback (most recent call last):
  File "/buildbot/buildarea/3.x.ware-freebsd.refleak/build/Lib/test/support/__init__.py", line 847, in gc_collect
    gc.collect()
    ~~~~~~~~~~^^
ResourceWarning: unclosed <socket.socket fd=8, family=2, type=1, proto=6, laddr=('127.0.0.1', 50293), raddr=('127.0.0.1', 50294)>
Task was destroyed but it is pending!
task: <Task pending name='Task-1973' coro=<BaseSelectorEventLoop._accept_connection2() done, defined at /buildbot/buildarea/3.x.ware-freebsd.refleak/build/Lib/asyncio/selector_events.py:217> wait_for=<Future pending cb=[Task.task_wakeup()]>>
Warning -- Unraisable exception
Exception ignored while calling deallocator <function _SelectorTransport.__del__ at 0x83ee27050>:
Traceback (most recent call last):
  File "/buildbot/buildarea/3.x.ware-freebsd.refleak/build/Lib/asyncio/selector_events.py", line 873, in __del__
    _warn(f"unclosed transport {self!r}", ResourceWarning, source=self)
    ~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ResourceWarning: unclosed transport <_SelectorSocketTransport closing fd=8>
k


Traceback (most recent call last):
  File "/buildbot/buildarea/3.x.ware-freebsd.refleak/build/Lib/test/support/__init__.py", line 847, in gc_collect
    gc.collect()
    ~~~~~~~~~~^^
ResourceWarning: unclosed <socket.socket fd=9, family=2, type=1, proto=6, laddr=('127.0.0.1', 52507), raddr=('127.0.0.1', 52508)>
Task was destroyed but it is pending!
task: <Task pending name='Task-1740' coro=<BaseSelectorEventLoop._accept_connection2() done, defined at /buildbot/buildarea/3.x.ware-freebsd.refleak/build/Lib/asyncio/selector_events.py:217> wait_for=<Future finished exception=ConnectionResetError()>>
Future exception was never retrieved
future: <Future finished exception=ConnectionResetError()>
Traceback (most recent call last):
  File "/buildbot/buildarea/3.x.ware-freebsd.refleak/build/Lib/asyncio/sslproto.py", line 581, in _on_handshake_complete
    raise handshake_exc
ConnectionResetError
Warning -- Unraisable exception
Exception ignored while calling deallocator <function _SelectorTransport.__del__ at 0x845339b50>:
Traceback (most recent call last):
  File "/buildbot/buildarea/3.x.ware-freebsd.refleak/build/Lib/asyncio/selector_events.py", line 873, in __del__
    _warn(f"unclosed transport {self!r}", ResourceWarning, source=self)
    ~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ResourceWarning: unclosed transport <_SelectorSocketTransport closing fd=9>
k

@freakboy3742

freakboy3742 commented Dec 13, 2025

Copy link
Copy Markdown
Contributor Author

And revert #142365, or give this a few days to check reliability?

As a follow up - there have been 9 CI runs that have involved a CI failure in the last 2 days; 8 of which involved failures on other platforms as well (so they're not iOS-specific problems). The one remaining failure was a failure downloading bzip2 binaries from GitHub.

So - it looks like this has fixed the problem.

@hugovk hugovk mentioned this pull request Dec 13, 2025
Merged
@hugovk

hugovk commented Dec 13, 2025

Copy link
Copy Markdown
Member

Excellent, let's revert! I've opened #142660.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@hugovk hugovk hugovk approved these changes

@ezio-melotti ezio-melotti Awaiting requested review from ezio-melotti ezio-melotti is a code owner

@AA-Turner AA-Turner AA-Turner is a code owner

Assignees

No one assigned

Labels

infra CI, GitHub Actions, buildbots, Dependabot, etc. skip news

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@freakboy3742 @mhsmith @bedevere-bot @hugovk