Story: Keep the compiler cache warm when a continuous job is cancelled
Table of Contents
This page documents a story in Sprint 28. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
A continuous run that is cancelled or times out still persists the compiler objects it produced, so the cache warms across runs instead of resetting.
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 28 |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-10-14 |
3. Acceptance
- The delete and save steps run when the CTest step ran, even if the job was cancelled.
- A run whose local cache is too small to help leaves the existing entry untouched.
- A normal completed run still replaces its entry as it does today.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Scaffold story: Keep the compiler cache warm when a continuous job is cancelled | DONE | 2026-10-14 | 2026-10-14 | Story scaffolding rides this task: documents, sprint wiring, and the scaffold PR. Close it before merging that PR. |
| Save the compiler cache on a cancelled or timed-out run | DONE | 2026-10-14 | 2026-10-14 | Initial task for: Keep the compiler cache warm when a continuous job is cancelled |