Repository navigation
Keep fuzz binaries out of the Ferrum target cache - #80
Merged
Merged
Conversation
Fuzz builds link each target into release/deps/<name>-<hash> and hard-link it to release/<name>. The uplifted copies were already excluded, but the deps outputs (about 3.65 GB for each of the 10 targets) were still archived. Since rolling run 17 every cargo-target save has filled the runner's separate /tmp mount while staging chunks. Exclude the deps outputs in both BoringCache plans and in the matching GitHub cache paths. The fuzz smoke step passed a fixed --target-scope. A scope's usage record travels with the cached target, so every job added to one active set and pruning could never evict an earlier job's outputs. Each job now uses its own scope. Prepare also prints /tmp usage and its mount. Docs: - https://boringcache.com/docs/adapters/cargo - https://github.com/actions/toolkit/tree/main/packages/glob#patterns
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.
Summary
x86_64-unknown-linux-gnu/release/deps/<target>-*for the 10 fuzz targets in both BoringCache plans and in the matching GitHub cache paths. The uplifted copies atrelease/<target>were already excluded, but thedeps/outputs (about 3.65 GB for each target) were still archived.--target-scopeper job (fuzz-smoke-<run id>-<attempt>). A scope's usage record travels with the cached target, so the fixedfuzz-smokescope added every earlier job's outputs to one active set and pruning could never evict them./tmpusage and its mount.Why
Every cargo-target save since run 17 (2026-10-15) has failed with a disk quota error (os error 122) while staging compressed chunks in
/tmp. On the ubuntu-26 runners/tmpis a separate mount of about 8 GB, and the saves failed at the same chunk count whether the root filesystem had 11 GB or 20 GB free. The last successful save, run 16, published 54.94 GB, and every later run restored that snapshot.Checks
bundle exec bin/bench check: 15 tools, 32 cases, okbash -non the fuzz smoke overlayDocs