ci: stop the linux runner OOMing on disk (CARGO_INCREMENTAL=0 + wider cleanup)#178
Merged
Conversation
… cleanup)
The linux job has been intermittently failing on "No space left on device" at the
trailing signerd test / rust-cache save — every real build/clippy/test step passes,
then target/ + the cache save overflow the runner. Two low-risk, no-new-dependency
changes:
1. CARGO_INCREMENTAL=0 (workspace env) — one-shot CI never reuses incremental
artifacts, so they are pure disk cost; off caps target/ growth across the
workspace build + tray build + tests + three --all-targets clippy passes.
2. Widen the pre-existing "Free up disk space" step: remove all of
/opt/hostedtoolcache (this job uses rustup + Foundry, not the hosted
python/node/go runtimes) plus node_modules/powershell/chromium/gcloud. The
step already runs before rust-cache/Foundry, so anything a later step needs is
recreated. Net ~+10 GB starting headroom on top of the smaller target/.
Raises the floor and lowers the peak, so the job stops depending on a lucky runner.
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
linuxjob has been intermittently failing onNo space left on deviceat the trailing signerd test / rust-cache save (hit on #171 and #175, each needing a manual re-run). Every real build/clippy/test step passes — thentarget/plus the cache save overflow the runner.Two low-risk, no-new-dependency changes:
CARGO_INCREMENTAL=0(workspaceenv) — one-shot CI never reuses incremental artifacts, so they're pure disk cost. Off capstarget/growth across the workspace build + tray build + tests + three--all-targetsclippy passes. Biggest single lever./opt/hostedtoolcache(this job uses rustup + Foundry, not the hosted python/node/go runtimes) plusnode_modules/powershell/chromium/gcloud. The step already runs before rust-cache/Foundry, so anything a later step needs is recreated. ~+10 GB starting headroom on top of the smallertarget/.Raises the floor and lowers the peak, so the job stops depending on a lucky runner. This PR self-validates —
pull_requestruns its ownci.yml, so a greenlinuxhere is the proof.Not switching to
jlumbroso/free-disk-space(reclaims more, but a third-party action in the supply chain) unless this proves insufficient — the hand-rolled expansion keeps zero new deps, matching the repo's posture.