Repository navigation
PR Test job times out at 60 minutes: the suite now takes about an hour #2257
Description
What's wrong
The Test job in pr_code_changes.yaml (and the same job in code_changes.yaml) has timeout-minutes: 60. Its comment says the job takes about 18 minutes. The suite now takes about an hour:
-
9 October. Successful PR runs took 57 to 60 minutes (for example
fix-hb-income-exclusions13:06 to 14:04,legacy-award-readers-claimant-partner16:06 to 17:06). -
10 October. Every PR
Testrun since 11:04Z was cancelled at the 60-minute limit:fix-uc-protected-lcwra-2026fix-additional-dwelling-purchase-2238fix-uc-standard-allowance-uplift-2239fix-pension-relief-annual-allowance-2237axiom-parity-check
Run 38051896891 was cancelled at 99% with every test passing.
So no pull request can currently get a green Test, and a rerun has the same odds.
Fix
Raise the limit to 120 minutes in both workflows, so a run that is merely slow finishes. That is still well under GitHub's 6-hour cap, which the limit exists to avoid.
Separately, the suite's runtime has roughly tripled since the comment was written (the property-based tests added since are the likely cause). Bringing it back down needs its own piece of work.
Activity
MaxGhenis commentedon Oct 10, 2026
Three more data points, from #2089:
#2089 merges once a
Testrun can finish, which #2258 allows.MaxGhenis commentedon Oct 12, 2026
Measured result: #2269 (shards) landed in rollup #2364 (merge f061b21) on 12 October.
Testjob ran the whole Python suite. Run 38075384588 took 59.6 min, and other runs were cancelled at the 60-minute limit (above).YAML took 4.2 min separately.
Still open: #2306 moves to four shards and fails CI on any unexpected skip, xfail or XPASS. #2331 cuts each shard's peak memory.