Separate aarch64 container builds onto different vms#2315
Merged
Conversation
Contributor
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
As a short-term solution to aarch64 container build jobs experiencing apt lock conflicts, we now have two additional aarch64 actions runners on a separate vm which Rocky 10 builds will fall on to.
owenjones
force-pushed
the
fix-aarch64-races
branch
from
eda87f9 to
21bb981
Compare
Alex-Welsh
approved these changes
May 19, 2026
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
2 participants
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.
As a short-term solution to aarch64 container build jobs experiencing apt lock conflicts, we now have two additional aarch64 actions runners on a separate vm which Rocky 10 builds will fall on to.
Test build