Repository navigation
chore: the mach cache key names the runner arch - #8
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The compiler cache key gains
${{ runner.arch }}:mach-${{ runner.os }}-${{ runner.arch }}-${{ env.MACH_VERSION }}-${{ env.MACH_REF }}.Without it an x64 and an arm64 runner on the same OS share one key. The default matrix runs one runner, but the
runnersdispatch input can name ubuntu-latest and ubuntu-24.04-arm together, and whichever saves first would serve its binary to the other.Decisions
Ran
actionlint on ci.yml. CI on this head missed the new key, built the compiler and passed.