From c01d9d3a9aaa48c96e22d8780c9b2f2aaf30f048 Mon Sep 17 00:00:00 2001 From: vringar Date: Sun, 6 Sep 2026 20:14:55 +0000 Subject: [PATCH] ci: bound the demo and pre-commit jobs Only the tests job sets timeout-minutes, so demo and pre-commit inherit GitHub's 360-minute default. Both are required status checks, so the merge queue waits on them, and its check_response_timeout_minutes cannot be derived from anything while two of the nine contexts it blocks on are bounded only by a six-hour default. A hung browser in demo would burn that before anything noticed. Ten minutes against observed runtimes of roughly two and a half minutes each. With this the bound is real: every required check is capped at 30 minutes, so the queue's 60-minute budget is that maximum plus an equal allowance for the runner wait, which sits inside the queue's window and inside no job timeout. --- .github/workflows/run-tests.yaml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/workflows/run-tests.yaml b/.github/workflows/run-tests.yaml index 82248b9675..59c5196a20 100644 --- a/.github/workflows/run-tests.yaml +++ b/.github/workflows/run-tests.yaml @@ -28,6 +28,7 @@ concurrency: jobs: pre-commit: runs-on: ubuntu-latest + timeout-minutes: 10 steps: - uses: actions/checkout@v4 - uses: ./.github/actions/setup @@ -35,6 +36,7 @@ jobs: demo: runs-on: ubuntu-latest + timeout-minutes: 10 steps: - uses: actions/checkout@v4 - uses: ./.github/actions/setup