Merge pull request 'ci: raise the Cargo target-dir limit to 60 GB' (#7 ) from ci/cargo-cache-limit into main

ci: raise the Cargo target-dir limit to 60 GB
The dev and test profiles together already take ~22 GB after one cold build, so the 25 GB limit would have wiped a warm cache within a build or two.
2026-09-22 16:08:41 +00:00 · 2026-09-22 08:45:15 -07:00
1 changed files with 4 additions and 2 deletions
@@ -51,10 +51,12 @@ jobs:
      # --no-run: the workflow compiled every test target without running them,
      # which catches a test that no longer builds without paying for the suite.
      - run: cargo test --workspace --locked --no-run
-      # Keep the cache from growing without bound: past 25 GB the target dir
+      # Keep the cache from growing without bound: past 60 GB the target dir
      # is dropped and the next build starts cold. The download cache stays.
+      # Two builds (dev + test profiles) already fill ~22 GB, so the limit
+      # has to sit well above that or it would wipe a warm cache every run.
      - if: always()
        run: |
          used=$(du -s --block-size=1G /cache/target 2>/dev/null | cut -f1)
          echo "target dir: ${used:-0} GB"
-          if [ "${used:-0}" -gt 25 ]; then rm -rf /cache/target && echo "over 25 GB: target dir cleared"; fi
+          if [ "${used:-0}" -gt 60 ]; then rm -rf /cache/target && echo "over 60 GB: target dir cleared"; fi
Author	SHA1	Message	Date
jcoffey-dev	ef068abbb1	Merge pull request 'ci: raise the Cargo target-dir limit to 60 GB' (#7 ) from ci/cargo-cache-limit into main ci / build (push) Canceled after 8m36s Details	2026-09-22 16:08:41 +00:00
jcoffey-dev	b37d252660	ci: raise the Cargo target-dir limit to 60 GB ci / build (pull_request) Successful in 22m47s Details The dev and test profiles together already take ~22 GB after one cold build, so the 25 GB limit would have wiped a warm cache within a build or two.	2026-09-22 08:45:15 -07:00