Repository navigation
ci: give the Windows Rust job 60 minutes so main can refill its cache - #79
Merged
Merged
Conversation
The Rust 1.98.1 bump in the upstream merge changed the rust-cache key, so the windows-msvc cache is empty. A cold run took 41m30s on train #78 and 45m+ on main b4c7b3d, which hit the 45-minute limit and cancelled. The cache only saves after a finished run on main, so every run stays cold and main stays red until one finishes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
QuicksilverSlick
added
lane:hotfix
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.
Hotfix: main is red. Main CI on b4c7b3d (train #78) was cancelled when
Rust / Windows Rust (x86_64-pc-windows-msvc)hit its 45-minute limit (run 40798023096). Every other job passed. The lane is hotfix-only, and the desktop release for tonight's merges is blocked.Why it timed out. The upstream merge (#75) bumped Rust to 1.98.1. That changed the
Swatinem/rust-cachekey, so thewindows-msvccache is empty:The cache saves only after a finished non-PR run, so each cancelled run leaves it empty. Main stays red until one run finishes inside the limit.
Change.
timeout-minutes: 45becomes60on that one job, with a comment saying why. After the first green main run the cache is warm again, and the job goes back to its usual time.Checked. The YAML parses, and an agent review approved it. This PR's own CI runs the Windows job (
_ci-*.ymlis in the rust paths filter), cold, so it tests the new limit, except for the cache save, which only push runs do.Where the time went (from the cancelled run): every build and test step had passed by 41m54s. The rust-cache post step then cleaned and compressed for about 3 minutes and was killed at 45:00, before it could upload. A cold run should finish in about 46-48 minutes, which leaves 12+ minutes of room. A
windows-latestimage update or cache eviction can empty this cache too: the repo is at 9.6 of its 10 GB Actions cache.Factory-Task: unblock red main (Windows Rust timeout after the Rust 1.98.1 bump)
Built-by: claude-code/claude-opus-5-5
Undo: revert this commit (the job goes back to 45 minutes)
🤖 Generated with Claude Code