From 1af4b42846027a29dbea3189d8df90d73cbb1158 Mon Sep 17 00:00:00 2001 From: lmoresi Date: Sat, 15 Aug 2026 17:45:56 +1000 Subject: [PATCH] CI: raise the job timeout to 120 minutes - the suite outgrew 60 Two PRs were cancelled at 1h00m and reported as failures when nothing had failed: the serial phase alone now takes ~55 minutes, so the parallel phase runs last and gets cut mid-run. A run with no additions at all (PR #568) took 55m07s, which means any new tests exceeded the cap. This is a stop-gap so work can land. The durable fix is splitting the batches across parallel jobs so wall-clock stops tracking total test time - filed separately. Underworld development team with AI support from Claude Code --- .github/workflows/build_uw3_and_test.yaml | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/.github/workflows/build_uw3_and_test.yaml b/.github/workflows/build_uw3_and_test.yaml index 1798bc766..19b5c631d 100644 --- a/.github/workflows/build_uw3_and_test.yaml +++ b/.github/workflows/build_uw3_and_test.yaml @@ -31,7 +31,14 @@ env: jobs: test: runs-on: ubuntu-latest - timeout-minutes: 60 + # The suite has outgrown 60 minutes. Measured 2026-08-15: the SERIAL phase + # alone is ~55 min (three batches at 14-15 min each), so the parallel phase + # - which runs last - was being cut off mid-run and reported as a failure + # that looked like a test failure. Any addition at all pushed a run over. + # This is a stop-gap that unblocks landing work; the durable fix is to split + # the batches across parallel jobs so wall-clock stops tracking total test + # time. See the CI-runtime issue for that. + timeout-minutes: 120 steps: - uses: actions/checkout@v4