Skip to content

EXPERIMENT crush-all-poles: disk-cache every bazel lane + rbe split + cargo MSRV pin - #14

Closed
b7r6 wants to merge 3 commits into
mainfrom
ci/crush-all-poles
Closed

b7r6 wants to merge 3 commits into
mainfrom
ci/crush-all-poles

Conversation

@b7r6

@b7r6 b7r6 commented Oct 2, 2026

Copy link
Copy Markdown
Owner

Non-blocking whole-CI experiment. Stacks: persistent disk cache on every bazel-test lane (native Bazel 9/8 + nix Bazel Dev), Tom's rbe-discovery split, and pins native-cargo to MSRV 1.97.1 to fix the toolchain-drift red lane. Goal: lower the MAX-lane (PR-gating) wall-clock, all green. Do not merge; does not touch hard-deck PR #6.

palfrey and others added 2 commits October 2, 2026 13:12
…split + MSRV pin

Whole-CI stacking to make the slowest lane (the PR gate) low, not one lane:
- native-bazel: persistent disk cache on ALL lanes (Bazel 9 + Bazel 8), not
  only when cloud is off. Bazel 8 is ~2.6% warm on the Bazel-9-keyed remote
  cache; measured 729s cold -> 148s warm with the disk cache.
- nix Bazel Dev: add actions/cache + --disk_cache to the nix-wrapped
  bazel test //... (same ~700s uncached-compile long pole, no setup-bazel knob).
- nix generate-rbe-commands: list-only target, drop the nativelink rebuild
  from discovery (124s -> 93s) [folds X4].
- native-cargo: pin windows-2022 + ubuntu to MSRV 1.97.1 instead of floating
  stable, which drifted ahead and hard-errored on a deprecation lint
  (fetch_update), reddening the lane for a toolchain reason. Keeps it green.

Co-Authored-By: Claude Opus 4.8 <[email protected]>
@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown

Some of the pull request description still needs filling in:

  • What and why is missing. Please keep the template's headings.
  • How was this verified? is missing. Please keep the template's headings.
  • Risk is missing. Please keep the template's headings.
  • AI assistance is missing. Please keep the template's headings.

Edit the description and this check re-runs on its own. The sections exist because they are the parts a reviewer cannot get from the diff: why the change is needed, how you know it works, what breaks if it is wrong, and which AI tools helped ("None" is a complete answer).

@b7r6

b7r6 commented Oct 3, 2026

Copy link
Copy Markdown
Owner Author

CI-spike measurement/experiment scratch — closing to keep the queue clean. Superseded by the single clean deliverable #25; branch retained if ever needed.

@b7r6 b7r6 closed this Oct 3, 2026
@b7r6
b7r6 deleted the ci/crush-all-poles branch October 15, 2026 11:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants