Skip to content

ci: stop the linux runner OOMing on disk (CARGO_INCREMENTAL=0 + wider cleanup) #178

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hellno merged 1 commit into from
Jul 2, 2026
Merged

ci: stop the linux runner OOMing on disk (CARGO_INCREMENTAL=0 + wider cleanup) #178

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 11 additions & 3 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,10 @@ on:

env:
CARGO_TERM_COLOR: always
# One-shot CI never rebuilds, so incremental artifacts are pure disk cost. Off keeps the Linux
# `target/` dir from outgrowing the freed disk across the workspace build + tray build + tests +
# three clippy passes (the linux job kept OOMing the runner on "No space left on device").
CARGO_INCREMENTAL: "0"

jobs:
# Fail-fast gate: formatting is OS-independent, so check it once, fast, before the heavy builds.
Expand All @@ -55,13 +59,17 @@ jobs:
- uses: actions/checkout@v4
# The dep tree (gpui + Helios/revm/bls + the Railgun ZK tree) overflows the stock ubuntu
# runner's ~14 GB and OOMs the build / cache-save — and the rust-cache RESTORE below extracts a
# multi-GB target dir that can itself exhaust the disk before anything builds. Reclaim ~20 GB of
# multi-GB target dir that can itself exhaust the disk before anything builds. Reclaim ~30 GB of
# preinstalled toolchains we never use FIRST, before the cache restore, so neither the restore
# nor the build runs out of space. (macOS runners have the headroom, so this is Linux-only.)
# nor the build runs out of space. This job uses rustup + Foundry, NOT any hosted-toolcache
# runtime (python/node/go), so the whole cache is dead weight here. (macOS has the headroom, so
# this is Linux-only.) Paired with CARGO_INCREMENTAL=0 above, which caps target/ growth.
- name: Free up disk space
run: |
sudo rm -rf /usr/local/lib/android /usr/share/dotnet /opt/ghc \
/opt/hostedtoolcache/CodeQL /usr/local/share/boost || true
/opt/hostedtoolcache /usr/local/share/boost \
/usr/local/lib/node_modules /usr/local/share/powershell \
/usr/local/share/chromium /usr/lib/google-cloud-sdk || true
sudo docker image prune --all --force >/dev/null 2>&1 || true
df -h /
- uses: Swatinem/rust-cache@v2
Expand Down
Loading