ci: route build IO through Dev Drives#31357
Draft
anp-oai wants to merge 2 commits into
Draft
Conversation
This was referenced Jul 7, 2026
2a2c345 to
251e09b
Compare
7163e06 to
1c3f5f3
Compare
anp-oai
commented
Jul 7, 2026
anp-oai
added a commit
that referenced
this pull request
Jul 7, 2026
251e09b to
088856e
Compare
1c3f5f3 to
c33c58b
Compare
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.
Why
Windows Cargo and Bazel jobs spend significant time in filesystem-heavy build and cache directories. Route those directories through one CI build root so Windows can use its Dev Drive and Unix can use a stable cache root.
What
setup-cidefineCI_BUILD_ROOT,CARGO_TARGET_DIR, Bazel cache/output paths, and temp paths.C:.Manual validation
just test-github-scripts.yq.Stack