docs(CI): timeout-minutes is not enforced on this runner, so the step timeout is the bound #1882

Merged
jaylouisw merged 1 commit from docs/1117-1815 into main 2026-11-17 18:26:06 +00:00
Owner

docs/CI.md said: "Every job also carries a timeout-minutes bound. A hung job on a single runner is not a slow job, it is a stopped queue ..." - written as the defence of the queue.

The tree says that bound does not exist in practice. .forgejo/workflows/ci.yml records the measurement twice, in the changes job (line 133) and again above the smoke step (line 618): timeout-minutes: 5 is "not enforced by this runner" - task 12980 (run 5238, pull #1851) reported Failing after 13m48s, task 10860 (run 4596) 12m45s, task 2694 (run 1342) 27,702 s, and all five jobs of that pull request read Blocked by required conditions throughout. That is why every fetch in ci.yml is wrapped in timeout 120 / timeout 300 with a 1 kB/s abort, and why the smoke client is bounded at 180 s (#1870) rather than by its timeout-minutes: 10.

Docs-only: the page now states the bound's real status and points at the step-level timeouts that do hold. No workflow, engine or script is touched.

Guards, all green: syntax-check 392 files; docs-cli-transcript 4; docs-show-commands 7 (54 forms, 108 commands typed); help-completeness 8 (102 advertised commands, 19 mechanisms, 16 shows); no-form-help-key 81; check-control-bytes clean; check-doc-citations 349 citations, exit 0.

`docs/CI.md` said: "Every job also carries a `timeout-minutes` bound. A hung job on a single runner is not a slow job, it is a stopped queue ..." - written as the defence of the queue. The tree says that bound does not exist in practice. `.forgejo/workflows/ci.yml` records the measurement twice, in the `changes` job (line 133) and again above the smoke step (line 618): `timeout-minutes: 5` is "not enforced by this runner" - task 12980 (run 5238, pull #1851) reported `Failing after 13m48s`, task 10860 (run 4596) 12m45s, task 2694 (run 1342) 27,702 s, and all five jobs of that pull request read `Blocked by required conditions` throughout. That is why every fetch in `ci.yml` is wrapped in `timeout 120` / `timeout 300` with a 1 kB/s abort, and why the smoke client is bounded at 180 s (#1870) rather than by its `timeout-minutes: 10`. Docs-only: the page now states the bound's real status and points at the step-level timeouts that do hold. No workflow, engine or script is touched. Guards, all green: syntax-check 392 files; docs-cli-transcript 4; docs-show-commands 7 (54 forms, 108 commands typed); help-completeness 8 (102 advertised commands, 19 mechanisms, 16 shows); no-form-help-key 81; check-control-bytes clean; check-doc-citations 349 citations, exit 0.
docs(CI): timeout-minutes is not a bound on this runner, the step's own timeout is (#1870's evidence)
All checks were successful
CI / Classify the change (pull_request) Successful in 10s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 16s
CI / Server smoke test (pull_request) Successful in 9s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 20) (pull_request) Successful in 54s
CI / Test (Node 18) (pull_request) Successful in 1m3s
CI / Test (Node 22) (pull_request) Successful in 1m0s
CI / Arm auto-merge (pull_request) Successful in 8s
5c37d7c0e8
jaylouisw force-pushed docs/1117-1815 from 5c37d7c0e8
All checks were successful
CI / Classify the change (pull_request) Successful in 10s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 16s
CI / Server smoke test (pull_request) Successful in 9s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 20) (pull_request) Successful in 54s
CI / Test (Node 18) (pull_request) Successful in 1m3s
CI / Test (Node 22) (pull_request) Successful in 1m0s
CI / Arm auto-merge (pull_request) Successful in 8s
to 48efeba6ec
All checks were successful
CI / Classify the change (pull_request) Successful in 14s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 20) (pull_request) Successful in 50s
CI / Test (Node 18) (pull_request) Successful in 58s
CI / Test (Node 22) (pull_request) Successful in 55s
CI / Arm auto-merge (pull_request) Successful in 18s
2026-11-17 18:23:58 +00:00
Compare
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!1882
No description provided.