Repository navigation
Run the cluster and Nix lanes on the AWS deployment only - #3245
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
MarcusSorealheis
approved these changes
Nov 20, 2026
This branch was successfully deployed
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
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.
What and why
The cluster and Nix lanes ran on git2prod for every branch and on the AWS deployment (
ci.nativelink.com) formainonly. git2prod's one shared client fails runs that have nothing to do with the change under test, and it retires. This makes the AWS jobs the only cluster and Nix jobs, for every repository branch:NativeLink / LinuxandBuild shared Nix packagekeep their names and artifacts; the Nix job again publishesnix-ci-packageand the command matrix the jobs below read.continue-on-errorand noNL_AWS_LANEgate.How was this verified?
python3 -m unittest discover -s .github/scripts -p 'test_*.py': 123 pass, 9 skipped. This branch's own push runs both lanes on AWS.Risk
Every branch now builds on AWS; the role and the environment allow it (TraceMachina/ci-acceleration#20, applied). Same-repo pull requests in #3243 read
cluster-ci-benchmark, which still points at git2prod.AI assistance
An agent drafted the change and I reviewed every line.