Skip to content

Fix Windows CI with cached builds and stay under the cache quota - #570

Merged
ludfjig merged 2 commits into
mainfrom
ci-cache-fixes
Nov 9, 2026
Merged

ludfjig merged 2 commits into
mainfrom
ci-cache-fixes

Conversation

@ludfjig

@ludfjig ludfjig commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

The first Prime Caches run on main saved 10.6 GB, over the 10 GB
repository quota. GitHub then evicts the least recently used entries,
and each push to main re-primes them. Windows entries came out larger
than estimated.

The Linux arm64 build entries take 1.9 GiB. Those jobs finished about 8
minutes before the slowest job in a fully cold run, so caching them does
not shorten PR CI. Dropping them brings the total to about 8.6 GB.

The prime job timeout default drops to 45 minutes. 90 minutes covered
two release builds on the 2-CPU Linux arm64 VMs, and the slowest
remaining job took 13 minutes.

Signed-off-by: Ludvig Liljenberg <4257730+ludfjig@users.noreply.github.com>
hyperlight-host builds hyperlight_surrogate.exe in target/<profile>/build/hls,
outside its OUT_DIR. rust-cache deletes that directory but keeps the
build script state, so Windows jobs that restore a primed cache fail to
compile hyperlight-host. Every Windows build, benchmark and code check
job fails this way once main has primed the caches.

Windows jobs now clean hyperlight-host after restoring the cache, so its
build script runs again. This matches hyperlight-js and can be removed
once hyperlight-host includes the fix that moves the surrogate into
OUT_DIR.

Signed-off-by: Ludvig Liljenberg <4257730+ludfjig@users.noreply.github.com>
@ludfjig
ludfjig merged commit ebffb67 into main Nov 9, 2026
51 of 52 checks passed
@ludfjig
ludfjig deleted the ci-cache-fixes branch November 9, 2026 22:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants