Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
freakboy3742 merged 2 commits intopython:mainfromfreakboy3742:ios-macos-runner
Dec 9, 2025

Conversation

@freakboy3742
Copy link
Contributor

@freakboy3742freakboy3742 commentedDec 9, 2025•
edited by bedevere-appbot
Loading

We're currently seeing a2-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 (seeactions/runner-images#12777).

This PR reverts to themacos-14 runner, which apparently isn't subject to the issues themacos-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
Copy link
ContributorAuthor

@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 reacted with rocket emoji

Copy link
Member

@hugovkhugovk left a comment

Choose a reason for hiding this comment

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

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

@hugovkhugovk added the infraCI, GitHub Actions, buildbots, Dependabot, etc. labelDec 9, 2025
@mhsmith
Copy link
Member

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

freakboy3742 and hugovk reacted with thumbs up emoji

@freakboy3742freakboy3742 merged commit9188483 intopython:mainDec 9, 2025
235 checks passed
@freakboy3742freakboy3742 deleted the ios-macos-runner branchDecember 9, 2025 21:52
@miss-islington-app
Copy link

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 requestDec 9, 2025
Switch to the macos-14 runner for iOS CI, working around some instabilityin the macos-15 runner.(cherry picked from commit9188483)Co-authored-by: Russell Keith-Magee <russell@keith-magee.com>
@bedevere-app
Copy link

GH-142494 is a backport of this pull request to the3.14 branch.

@bedevere-appbedevere-appbot removed the needs backport to 3.14bugs and security fixes labelDec 9, 2025
freakboy3742 added a commit that referenced this pull requestDec 9, 2025
…142494)Switch to the macos-14 runner for iOS CI, working around some instabilityin the macos-15 runner.(cherry picked from commit9188483)Co-authored-by: Russell Keith-Magee <russell@keith-magee.com>
@bedevere-bot
Copy link

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

Hi! The buildbotAMD64 FreeBSD Refleaks 3.x (tier-3) has failed when building commit9188483.

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/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", line847, ingc_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 exceptionException 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", line873, in__del__    _warn(f"unclosed transport{self!r}",ResourceWarning,source=self)~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ResourceWarning:unclosed transport <_SelectorSocketTransport closing fd=8>kTraceback (most recent call last):  File"/buildbot/buildarea/3.x.ware-freebsd.refleak/build/Lib/test/support/__init__.py", line847, ingc_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 retrievedfuture:<Future finished exception=ConnectionResetError()>Traceback (most recent call last):  File"/buildbot/buildarea/3.x.ware-freebsd.refleak/build/Lib/asyncio/sslproto.py", line581, in_on_handshake_completeraise handshake_excConnectionResetErrorWarning -- Unraisable exceptionException 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", line873, in__del__    _warn(f"unclosed transport{self!r}",ResourceWarning,source=self)~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ResourceWarning:unclosed transport <_SelectorSocketTransport closing fd=9>k

@freakboy3742
Copy link
ContributorAuthor

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). Theone remaining failure was a failure downloading bzip2 binaries from GitHub.

So - it looks like this has fixed the problem.

@hugovk
Copy link
Member

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

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

Reviewers

@hugovkhugovkhugovk approved these changes

@ezio-melottiezio-melottiAwaiting requested review from ezio-melottiezio-melotti is a code owner

@AA-TurnerAA-TurnerAwaiting requested review from AA-TurnerAA-Turner is a code owner

Assignees

No one assigned

Labels

infraCI, 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
[8]ページ先頭
©2009-2026 Movatter.jp