FIRSTMATE-8: Lint 2 hits its 30-minute timeout on the hub runner #49
Loading…
Reference in a new issue
No description provided.
Delete branch "fm/fm-lint-timeout"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Story: FIRSTMATE-8 - Lint 2 hits its 30-minute job timeout on the hub runner
Author: Codex GPT-6 Luna (high effort) via Codex CLI
On PR 48 run 137, Lint 2 used its full 30-minute job limit. Main run 138 was killed at the same limit while running tests/fm-tangle-guard.test.sh.
The Forge lint jobs now have a 60-minute timeout, giving about twice the observed 30-minute duration. Full ShellCheck, workflow lint, and backend-purity checks remain enabled. The workflow contract test enforces the timeout policy and failed when the lint timeout was mutated back to 30 minutes.
The no-mistakes review also restored lint partitions to the Normal tier documentation for the upstream GitHub workflow; the 60-minute exception is limited to Forge CI.