The repository's Actions cache is over the 10 GB per-repository limit, so GitHub is evicting the least recently used entries, and the mutation workflow's incremental reports are among what gets evicted. A full main run dispatched at 15:53Z saved a cache per mutation slice; a few hours later only five of those were still there, and the next full run started those slices cold (a slice that took a few minutes warm takes an hour or more cold).
What gh api repos/ExaDev/documents.js/actions/cache/usage and the cache list show right now: 175 active caches, about 11.5 GB. By key family the volume is turbo-test (38 entries, about 5.9 GB, roughly 156 MB each), node-cache (11, 2.75 GB), turbo-typecheck (9, 0.9 GB) and turbo-lint (8, 0.8 GB). The mutation entries are tiny by comparison: mutation-incremental is 41 entries and about 30 MB in all. The turbo entries come from .github/actions/setup-workspace, whose key ends in github.run_id, so every run writes a new near-duplicate entry instead of replacing one.
I haven't changed anything about it. Fixing it means changing how the shared setup action keys its turbo cache, which affects every CI job, so it's its own change. Until then the nightly mutation run mostly runs cold, which the slice sizing already tolerates, but it is the difference between minutes and hours per slice.
The repository's Actions cache is over the 10 GB per-repository limit, so GitHub is evicting the least recently used entries, and the mutation workflow's incremental reports are among what gets evicted. A full main run dispatched at 15:53Z saved a cache per mutation slice; a few hours later only five of those were still there, and the next full run started those slices cold (a slice that took a few minutes warm takes an hour or more cold).
What
gh api repos/ExaDev/documents.js/actions/cache/usageand the cache list show right now: 175 active caches, about 11.5 GB. By key family the volume isturbo-test(38 entries, about 5.9 GB, roughly 156 MB each),node-cache(11, 2.75 GB),turbo-typecheck(9, 0.9 GB) andturbo-lint(8, 0.8 GB). The mutation entries are tiny by comparison:mutation-incrementalis 41 entries and about 30 MB in all. The turbo entries come from.github/actions/setup-workspace, whose key ends ingithub.run_id, so every run writes a new near-duplicate entry instead of replacing one.I haven't changed anything about it. Fixing it means changing how the shared setup action keys its turbo cache, which affects every CI job, so it's its own change. Until then the nightly mutation run mostly runs cold, which the slice sizing already tolerates, but it is the difference between minutes and hours per slice.