CI time limit on the step; no timeout in Dockerfile or scripts (closes #199)
check / check (push) Successful in 4m28s

The runner ignores a job's timeout-minutes, so the 20-minute limit moves
to the step that runs script/cibuild. The Dockerfile frontend-test stage,
script/frontend-test and script/frontend-viewport-test drop their timeout
wrappers, which failed make check on a busy host. go test's -timeout 90s
stays, as REPO_POLICIES.md requires it.

Model: opus-5-5
This commit is contained in:
clawbot committed 2026-11-10 20:13:05 +00:00
1 parent 437e0ea80c
commit ee7ab101aa
5 files changed
+15 -10

No files matched your search

+3 -2
View File
@@ -7,8 +7,6 @@ concurrency:
jobs:
check:
runs-on: ubuntu-latest
# Free the shared runner from a hung build.
timeout-minutes: 20
steps:
# actions/checkout v4.2.2, 2026-02-22
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683
@@ -17,4 +15,7 @@ jobs:
persist-credentials: false
# All history and tags, so git describe finds the version tag.
fetch-depth: 0
# Free the shared runner from a hung build. The limit is on the
# step because the runner ignores a job's timeout-minutes.
- run: script/cibuild
timeout-minutes: 20