zozo123 opened a new pull request, #73182:
URL: https://github.com/apache/airflow/pull/73182

   Preserve repairs made to restored prek environments and avoid clearing 
unrelated host caches. A repaired pull-request cache is republished by an 
eligible writer, so subsequent jobs can reuse it; a healthy pull-request hit 
still skips compression and upload.
   
   The existing refresh behavior for all non-PR runs (including push, schedule, 
and manual runs), two-day retention, and upstream compression settings are 
preserved. Readers never upload. Missing or unusable archives are treated as 
misses, and uncertain repair detection conservatively saves after successful 
installation.
   
   Repair detection compares shallow prek installation markers across the 
existing bounded installation retries. Namespace v13 avoids older archives 
containing manual-only skill-evaluation environments; those environments remain 
excluded as on current main. Phase timings and save reasons remain available 
for CI evaluation.
   
   Validation: 24 focused tests pass, including push/manual refresh coverage 
and real prek 0.5.2 repair → archive → restore → reuse. Regular static checks, 
scripts mypy, Ruff, and applicable manual checks pass.
   
   The earlier [warm-cache 
run](https://github.com/apache/airflow/actions/runs/35130234556/job/104914616259)
 and [cold-cache 
run](https://github.com/apache/airflow/actions/runs/35338574367/job/105582965496)
 used different v12 configurations. They demonstrate cache paths, not a 
controlled speedup for this revision. No numerical performance improvement is 
claimed.
   
   Split from #73124.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [x] Yes — Codex (GPT-6)
   
   Generated-by: Codex (GPT-6) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to