The canonical check workflow sets no time limit on its job #120

New Issue

2026-10-06T16:00:33+02:00

clawbot commented

2026-10-06 16:00:33 +02:00

The canonical .gitea/workflows/check.yml gives the check job no timeout-minutes, so a hung script/cibuild holds the shared runner until the runner's own default limit (hours). Repositories that vendor it byte-identical lose any limit they had: AutistMask's check job had timeout-minutes: 10 from sneak/AutistMask#294 and lost it in its re-vendor, sneak/AutistMask#474.

Definition of done

The canonical check.yml sets timeout-minutes on the check job, with a value that fits the slowest consuming repository's script/cibuild.
REPO_POLICIES.md names the limit, if it describes the workflow.

Model: opus-5-5

The canonical `.gitea/workflows/check.yml` gives the `check` job no `timeout-minutes`, so a hung `script/cibuild` holds the shared runner until the runner's own default limit (hours). Repositories that vendor it byte-identical lose any limit they had: AutistMask's `check` job had `timeout-minutes: 10` from https://git.eeqj.de/sneak/AutistMask/issues/294 and lost it in its re-vendor, https://git.eeqj.de/sneak/AutistMask/pulls/474. ## Definition of done - [ ] The canonical `check.yml` sets `timeout-minutes` on the `check` job, with a value that fits the slowest consuming repository's `script/cibuild`. - [ ] `REPO_POLICIES.md` names the limit, if it describes the workflow. Model: opus-5-5

clawbot commented

2026-10-07 10:33:45 +02:00

Plan:

.gitea/workflows/check.yml: timeout-minutes: 20 on the check job, with a one-line comment.
Why 20: script/cibuild runs three Docker builds (the lint phase, the test phase, then the image, which runs both phases again), each held to the 5-minute build limit in prompts/REPO_POLICIES.md, plus the bootstrap. 20 minutes covers that, and the slowest run measured so far (bsfirehose, 454 s on the loaded build host, #113).
prompts/REPO_POLICIES.md (the workflow paragraph) and both checklists (prompts/NEW_REPO_CHECKLIST.md, prompts/EXISTING_REPO_CHECKLIST.md) name the limit where they list what the workflow sets; last_modified bumped; a TODO.md Completed Steps entry in the same commit.

Judgement call: the value follows the current 5-minute build limit. If the answer on #113 changes that limit, the value follows it.

Model: opus-5-5

Plan: - `.gitea/workflows/check.yml`: `timeout-minutes: 20` on the `check` job, with a one-line comment. - Why 20: `script/cibuild` runs three Docker builds (the lint phase, the test phase, then the image, which runs both phases again), each held to the 5-minute build limit in `prompts/REPO_POLICIES.md`, plus the bootstrap. 20 minutes covers that, and the slowest run measured so far (`bsfirehose`, 454 s on the loaded build host, https://git.eeqj.de/sneak/prompts/issues/113). - `prompts/REPO_POLICIES.md` (the workflow paragraph) and both checklists (`prompts/NEW_REPO_CHECKLIST.md`, `prompts/EXISTING_REPO_CHECKLIST.md`) name the limit where they list what the workflow sets; `last_modified` bumped; a `TODO.md` Completed Steps entry in the same commit. Judgement call: the value follows the current 5-minute build limit. If the answer on https://git.eeqj.de/sneak/prompts/issues/113 changes that limit, the value follows it. Model: opus-5-5

clawbot referenced this issue from a commit

2026-10-07 10:37:41 +02:00

Set a time limit on the canonical check job (closes #120)

clawbot referenced a pull request that will close this issue

2026-10-07 10:37:52 +02:00

Set a time limit on the canonical check job (closes #120) #121

clawbot commented

2026-10-07 10:37:59 +02:00

Built in #121 as planned: timeout-minutes: 20 on the check job, named in REPO_POLICIES.md and both checklists. README.md does not describe what the workflow sets and is unchanged.

Model: opus-5-5

Built in https://git.eeqj.de/sneak/prompts/pulls/121 as planned: `timeout-minutes: 20` on the `check` job, named in `REPO_POLICIES.md` and both checklists. `README.md` does not describe what the workflow sets and is unchanged. Model: opus-5-5

clawbot referenced this issue from a commit

2026-10-07 11:05:40 +02:00

Set a time limit on the canonical check job (closes #120)

clawbot closed this issue

2026-10-07 11:31:36 +02:00

clawbot referenced this issue from a commit

2026-10-07 11:31:37 +02:00

Set a time limit on the canonical check job (closes #120)

Sign in to join this conversation.