CI: Pin version of macos to avoid build failure #998
Merged
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
thedataking
force-pushed
the
perl/fix-macos-cargo-not-found
branch
2 times, most recently
from
7955fbc
to
1c50f1b
Compare
thedataking
changed the title
Also pins the macos version so we don't get silently switched to aarch64 which is tested separately.
thedataking
force-pushed
the
perl/fix-macos-cargo-not-found
branch
from
1c50f1b
to
248ad25
Compare
thedataking
changed the title
randomPoison
approved these changes
Apr 23, 2024
|
Can we add a test for |
that's already covered in another workflow file ( |
Ah, okay. Awesome then! |
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.
It seems
macos-latesttransitioned (is transitioning) fromx86toaarch64. This may lead to unintended interactions with caching of the Rust toolchain. We've observed runs that failed becausecargowas not found. My best guess is that we restored ax86toolchain onto aaarch64host but reproducing to make sure would take too much time. Requestingmacos-13instead ofmacos-latestshould avoid this issue altogether.