Skip to content
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

Sunset apple-silicon-m1 self-hosted runner, as now is supported by Github Hosted runners via macos-latest tag. Use macos-13 for runs on Intel macs #8713

Merged
merged 1 commit into from
May 1, 2024

Conversation

misl6
Copy link
Member

@misl6 misl6 commented May 1, 2024

Maintainer merge checklist

  • Title is descriptive/clear for inclusion in release notes.
  • Applied a Component: xxx label.
  • Applied the api-deprecation or api-break label.
  • Applied the release-highlight label to be highlighted in release notes.
  • Added to the milestone version it was merged into.
  • Unittests are included in PR.
  • Properly documented, including versionadded, versionchanged as needed.

The time has come, as being announced in https://github.blog/changelog/2024-04-01-macos-14-sonoma-is-generally-available-and-the-latest-macos-runner-image , macos-latest on kivy/kivy repo is already targeting macos-14, which is an Apple Silicon runner.

Therefore, our self-hosted apple-silicon-m1 runner, after ~1.5 years of service will start the sunset phase.

However, now comes an additional issue: "How can we make sure to properly test things for Intel Macs?".

As ATM https://github.com/orgs/community/discussions/116568, is still unanswered, targeting macos-13 for testing on an Intel runner looks like the best (free of charge) choice.
I guess the long-time alternative is macos-latest-large, which is a macos-14 image that runs on Intel Macs, but is quite pricey for us.

What will be the future of apple-silicon-m1 runner hardware?

  • iOS Simulators?
  • Android Emulators?

…thub-hosted runners. Use macos-13 for runs on Intel macs
@misl6 misl6 changed the title Sunset apple-silicon-m1 self-hosted runner, as now is supported by github-hosted runners. Use macos-13 for runs on Intel macs Sunset apple-silicon-m1 self-hosted runner, as now is supported by Github Hosted runners via macos-latest tag. Use macos-13 for runs on Intel macs May 1, 2024
@misl6 misl6 added the Component: tests/CI Tests, CI, GitHub settings label May 1, 2024
@misl6 misl6 added this to the 3.0.0 milestone May 1, 2024
@misl6 misl6 merged commit 9bb694f into kivy:master May 1, 2024
29 checks passed
Copy link

github-actions bot commented Sep 7, 2024

The backport to devel-2.3.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-devel-2.3.x devel-2.3.x
# Navigate to the new working tree
cd .worktrees/backport-devel-2.3.x
# Create a new branch
git switch --create backport-8713-to-devel-2.3.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 9bb694f9e6bf065515c019594e603206753a1e5b
# Push it to GitHub
git push --set-upstream origin backport-8713-to-devel-2.3.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-devel-2.3.x

Then, create a pull request where the base branch is devel-2.3.x and the compare/head branch is backport-8713-to-devel-2.3.x.

kivybot pushed a commit that referenced this pull request Sep 7, 2024
…Github Hosted runners via `macos-latest` tag. Use `macos-13` for runs on Intel macs (#8713)

(cherry picked from commit 9bb694f)
misl6 added a commit that referenced this pull request Sep 7, 2024
…Github Hosted runners via `macos-latest` tag. Use `macos-13` for runs on Intel macs (#8713) (#8820)

(cherry picked from commit 9bb694f)

Co-authored-by: Mirko Galimberti <me@mirkogalimberti.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant