Repository navigation
Push-to-main Test job times out at 60 minutes, so no release has gone out since 16 Oct #640
Description
Problem
push.yaml's Test job still has timeout-minutes: 60. #631 raised the same job in pr_code_changes.yaml to 90 minutes on 15 Oct, after the suite grew. Test jobs in push runs on main since 14 Oct took:
| Python | Successful runs |
|---|---|
| 3.11 | 33–54 min (n=16) |
| 3.12 | 32–56 min (n=15) |
| 3.13 | 36–60 min (n=16) |
| 3.14 | 23–42 min (n=18) |
Every push run on main on 16 Oct had Test jobs cancelled at exactly 60 minutes:
- the merge of Refuse disclosure codes that match nothing, and key UK regions on GSS codes #638 (run 38899177987);
- the merge of Close the receipt stack's outstanding review Lows #632 (run 38901635564);
- the merge of Qualify UK model and data candidates automatically before promotion #574 (run 38906243015).
Versioning needs Test, so it was skipped each time. With no "Update package version" commit, there is no Publish and no consumer dispatch: no PyPI release, no policyengine-release dispatch to the API, sim-api, the Budget dashboard or the scorecard. Automatic UK promotion (#635) moves main, then relies on this same release path.
Fix
Raise push.yaml's Test timeout to 90 minutes, matching #631, and record the current durations in its comment.
🤖 Generated with Claude Code
Activity