CI Issue
None of the four workflows in .github/workflows/ (ci.yml, publish-image.yml, maintenance-audit.yml, update-homebrew-formula.yml) set timeout-minutes on any job. Every job therefore falls back to GitHub Actions' default 360-minute (6 hour) timeout.
Evidence
Checked all four workflow files (.github/workflows/*.yml) — none contain a timeout-minutes key at the job level. Recent runs (gh run list) complete in well under 3 minutes each, so a hang in any step (a stalled podman build, a stuck unittest run, a network stall against the GitHub API in maintenance-audit.yml) would occupy a runner for up to 6 hours before GitHub kills it, instead of failing fast.
This is distinct from PR #131 (fix/audit-subprocess-timeouts), which bounded the maintenance audit script's own internal subprocess calls — it did not add a job-level timeout-minutes to the workflow itself.
Recommendation
Add a timeout-minutes value to each job, sized generously above observed run times (jobs currently run in 30s-3m):
ci.yml: test (~20m), publish-coverage (~10m), container-build (~20m)publish-image.yml: publish (~15m)maintenance-audit.yml: audit (~10m)update-homebrew-formula.yml: update (~10m)
Filed by ci-maintainer agent (ACMM L4/L5 — hold-gated mode)
🐝 Hive Agent: ci-maintainer | Instance: hive-wild-mole | SHA: unknown
— hive: agent=ci-maintainer backend=claude model=claude-sonnet-5 claude=2.1.226
CI Issue
None of the four workflows in
.github/workflows/(ci.yml,publish-image.yml,maintenance-audit.yml,update-homebrew-formula.yml) settimeout-minuteson any job. Every job therefore falls back to GitHub Actions' default 360-minute (6 hour) timeout.Evidence
Checked all four workflow files (
.github/workflows/*.yml) — none contain atimeout-minuteskey at the job level. Recent runs (gh run list) complete in well under 3 minutes each, so a hang in any step (a stalledpodman build, a stuckunittestrun, a network stall against the GitHub API inmaintenance-audit.yml) would occupy a runner for up to 6 hours before GitHub kills it, instead of failing fast.This is distinct from PR #131 (
fix/audit-subprocess-timeouts), which bounded the maintenance audit script's own internal subprocess calls — it did not add a job-leveltimeout-minutesto the workflow itself.Recommendation
Add a
timeout-minutesvalue to each job, sized generously above observed run times (jobs currently run in 30s-3m):ci.yml:test(~20m),publish-coverage(~10m),container-build(~20m)publish-image.yml:publish(~15m)maintenance-audit.yml:audit(~10m)update-homebrew-formula.yml:update(~10m)Filed by ci-maintainer agent (ACMM L4/L5 — hold-gated mode)
🐝 Hive Agent:
ci-maintainer| Instance:hive-wild-mole| SHA:unknown— hive: agent=ci-maintainer backend=claude model=claude-sonnet-5 claude=2.1.226