Repository navigation
Windows native desktop rows need about 120 minutes without a Rust cache #368
Description
What we measured
"Native desktop - Windows arm64" on commit 706d63b (CI run 43523947929), with no Rust cache, twice ran every step successfully and was then cancelled at its 120-minute limit during the post steps. On the pull request run 43496452314 the same job took 113 minutes and Windows x64 took 108, also with no cache.
Long steps in the cancelled attempt:
| Step | Minutes |
|---|---|
| Build native bundle without publishing | 44 |
| Run background Git index lock tests (Windows) | 21 |
| Test desktop Rust host | 19 |
| Run Git system configuration tests (Windows) | 10 |
| Check Windows server test targets compile | 7 |
| Post Cache Rust build output | 5 |
What is already done
A pull request raises both Windows rows to 180 minutes. That stops the cancellations but does not make the job shorter.
What is open
- About 38 minutes of the row are server tests. The macOS rows moved theirs into a job of their own; the same split may fit Windows.
- A job cancelled by the time limit does not save its cache, so the next run is cold again. Two attempts in a row were cold for that reason or because the cache entry was missing; which one is not known.
- No full job time with a warm cache has been measured.
Activity
mubeda commentedon Nov 14, 2026
Measured in pull request 370 (2026-11-14).
bibcode-serverfive times: the desktop host tests,cargo check --all-targets, two server test builds and the release bundle. Those Cargo builds took 76 of the arm64 row's 103 minutes; running the tests took about 2.