You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Rene Cannao 18d4d92eab ci(cache): drop pre-compression from zstd --ultra -22 to zstd -15 ... Follow-up to 4e4d4496a, which introduced pre-compression at `--ultra -22` to fit the _test/_bin caches under GitHub's 10 GB per-repo cache quota. The size win is real, but the time cost was not properly accounted for: Last green CI-builds run (97eab1bbf0): ubuntu24-tap-genai-gcov: build 17m58s, pack-bin 3m11s, pack-test 15m53s ubuntu22-tap: build 17m54s, pack-bin 2m51s, pack-test 14m08s `pack-test` alone takes roughly as long as the actual build at `--ultra -22`, pushing CI-builds wall clock to ~38 min and gating every downstream TAP-group workflow on it. With PR #5827/#5828 fanning coverage out to ~38 TAP groups, the compounded idle time was intolerable. Switching to zstd -15: - keeps actions/cache@v4 free of double compression (already- compressed .tar.zst is essentially a no-op on the action's own level-3 pass), preserving the original anti-LRU motivation; - captures most of the size headroom -- empirically -15 vs --ultra -22 trades roughly 5-7% extra blob size for ~10x faster compression; - takes pack-test from ~15 min down to an expected 1-3 min per ubuntu job, cutting ~12-14 min off the critical path of every CI-builds invocation. If the quota turns out to be too tight at -15 we can revisit -19 (the canonical "high-compression sweet spot"), but -22 --ultra was clearly over the line. No changes to cache keys, no consumer-side changes needed -- the .tar.zst format is identical, only the compression level inside the blob differs.		2 weeks ago
..
workflows	ci(cache): drop pre-compression from zstd --ultra -22 to zstd -15	2 weeks ago
issue_template.md	Rewrite and formatting change to issue template	6 years ago