chore: use the macOS 13 runner #523
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
satya164
force-pushed
the
@atlj/use-macos-13-runner
branch
from
f79444d
to
2017e91
Compare
|
Closed this one because macOS 14 runners are better |
|
I guess the root cause of this issue is the version of Xcode not the macOS version. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Currently,
macOS 12has issues with pod installation. It fails due to theglogdependency. This changes the runner version tomacOS 13. I've also created a PR for using themacOS 14runners, however seems like the availability of those machines are low at the moment so the CI takes a long time to run.#518
expo/expo#25905
Test plan
We need to make sure macos related runners pass on CI.