Skip to content

ci(test): free the local kache store before running the tests - #522

Closed
raphaelvigee wants to merge 1 commit into
masterfrom
raphaelvigee/ci-free-kache-store
Closed

raphaelvigee wants to merge 1 commit into
masterfrom
raphaelvigee/ci-free-kache-store

Conversation

@raphaelvigee

Copy link
Copy Markdown
Member

Test linux/arm64 now fails with ENOSPC on any branch. The same commit (ab245af5) passed at 02:04 on 2026-10-29 and failed at 09:09 (diagnostic #520).

Cause: on ext4, kache's local store ends the compile with 45–57 GiB of physical blobs behind a 10 GiB logical size, because evicted entries leave their blobs behind (kache stats: Dedup: 567 unique blobs, 44.7 GiB physical versus about 10.9 GiB on green runs). plugingo-e2e then fills the rest of the root disk unpacking Go toolchains.

Fix: compile with tst --no-run, then (Linux only) stop the daemon, which drains the uploads, and drop the local store, keeping its log for the drain step. Then run tst against the complete target/. The store isn't read again in this job.

Not linted locally: the change is workflow YAML only (checked to parse).

Blocks #516.

🤖 Generated with Claude Code

…e tests

On the linux runners kache's local store has started ending a compile at
45-57 GiB of physical blobs behind its 10 GiB logical size (evicted entries
leave their blobs), and plugingo-e2e then fills the root disk: Test
linux/arm64 fails with ENOSPC. The same commit that passed at 02:04 on
2026-10-29 (ab245af) fails this way since, so it is not a code change.

Compile with `tst --no-run`, stop the daemon (which drains the uploads),
drop the store, then run `tst` against the complete target/.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@raphaelvigee

Copy link
Copy Markdown
Member Author

Closing: this does not fix it. The step cleared the store, but 88G stayed used afterwards (the store's blobs are largely shared with target/), and plugingo-e2e still hit ENOSPC. The explanation in the commit message is wrong. The arm64 disk issue needs its own investigation (a du breakdown of target/ vs the kache store on a red run).

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.

1 participant