fix(ci): keep the job-local cache alive during long compilations #464
No reviewers
Labels
No labels
code-review
correctness
dos
performance
security
severity/high
severity/low
severity/medium
tech-debt
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
h-dv/code-index!464
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/compiler-cache-active-requests"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Long compilations can outlast sccache 0.15's idle timer, causing an active request to lose its server and compile again through fallback. Disable that timer before starting the job-local server and carry the setting into subsequent CI steps. Disposable job containers bound its lifetime; fallback and backend credential redaction remain intact.
Validation: all 22 Python CI controls pass, including three executed cache-setup controls. The new timeout control fails with the old setup. In the pinned CI image, a real GCC compilation through the actual setup script reproduces the baseline shutdown and duplicate compilation (27.024s), while the candidate compiles once (15.036s) and returns a warm hit in 0.005s with the same object hash. This isolates the idle-timeout mechanism; the historical CI server exit reasons remain unmeasured.
Fixes #437.
Merged normally after all four exact-head workflows passed on
40fbe0938d: Windows 6675 (44m04s), core 6676 (40m50s), packages 6677, pilots 6678. Fetched merge047c915a6d; source head is a merged ancestor and both trees equal18c61c1592. No force merge or qualification waiver. The CI fix now applies to subsequent runs; the runtime release batch is still being validated.