-
-
Notifications
You must be signed in to change notification settings - Fork 32k
gh-133131: Discover an appropriate iOS simulator rather than hard-coding iPhone SE 3rd gen #133132
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
!buildbot iOS |
🤖 New build scheduled with the buildbot fleet by @freakboy3742 for commit 3c9e818 🤖 Results will be shown at: https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F133132%2Fmerge The command will test the builders whose names match following regular expression: The builders matched are:
|
Thanks @freakboy3742 for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13. |
…rd-coding iPhone SE 3rd gen (pythonGH-133132) Determines a candidate simulator at runtime rather than hardcoding iPhone SE. (cherry picked from commit 42b0b06) Co-authored-by: Russell Keith-Magee <[email protected]>
GH-133173 is a backport of this pull request to the 3.13 branch. |
…ard-coding iPhone SE 3rd gen (GH-133132) (#133173) Determines a candidate simulator at runtime rather than hardcoding iPhone SE. (cherry picked from commit 42b0b06) Co-authored-by: Russell Keith-Magee <[email protected]>
|
# consistent over time. Older Xcode versions will use "iPhone SE (Nth | ||
# generation)"; As of 2025, they've started using "iPhone 16e". | ||
# | ||
# When Xcode is updated after a new release, new devices will be available |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excelente
With the release of the iPhone 16e, Xcode 16.3 has been released; this release no longer contains an iPhone SE (3rd generation) simulator by default.
This PR modifies the iOS testbed to search for "SE-class" deployment candidates, rather than hard-coding the iPhone SE as the deployment target if no simulator image is specified.