ci(canary-rollout): raise the gate job timeout 30 -> 60 min so a sweep finishes and leaves logs

Merged
DO
1mo ago
+31-2

Summary

One-line change (plus an explanatory comment): timeout-minutes: 30 -> 60 on the canary job in .github/workflows/canary-rollout.yml. Requested/approved by the repo owner in the session driving issue 1259.

Why. The last 7 consecutive scheduled sweeps (from 2026-10-07 15:43Z through 2026-10-09 15:31Z, on both the #1260 and #1262 code) were all killed at the 30-minute job timeout:

scheduled run (UTC)durationconclusion
10-09 15:3135.0 mincancelled
10-09 06:3435.0 mincancelled
10-08 21:2642.5 mincancelled
10-08 15:4835.0 mincancelled
10-08 06:3235.0 mincancelled
10-07 21:3035.1 mincancelled
10-07 15:4335.1 mincancelled
10-07 06:2128.4 minsuccess

Two consequences: (1) the second gate step (sync-issues: blocker issues + fleet-status summary) never ran in those sweeps, so those outputs went stale; (2) GitHub keeps no logs for a job cancelled by its timeout (BlobNotFound, also for the steps that finished), so the canary timing output added in #1260 could not be read, and the effect of #1262 (date-bounded ingress lists) cannot be measured. The one good sample (10-07 06:21Z, run 37581060882) showed 99% of each gate step inside gh, ~80% of it in gh run list.

60 minutes lets a sweep finish and leave logs. It matches the 60-minute jobs elsewhere in the org standards (standards/ci-standards.md). It is meant to be revisited: once the gate steps are back near their pre-#1238 ~10 min each, the timeout can come back down.

Risk

Low. A genuine hang is bounded at 60 instead of 30 minutes. Because the fleet concurrency group has cancel-in-progress: false, a longer sweep can delay the next scheduled one (GitHub keeps one pending run), which is already the case today with the 35-minute cancelled runs. No script or gate logic changes.

Test plan

  • Existing canary-rollout.yml: canary job timeout-minutes ... bats guards (declares one; at least 20 min) pass.
  • YAML parses. The workflow's behavior is otherwise unchanged.

Rollback

Revert this PR.

Next

After merge, a manual workflow_dispatch (also approved by the owner) produces one completed run whose canary timing blocks can be read, to see whether the ingress run-list cost (#1262) is still dominant. Refs #1259, #1262, #1260.

šŸ¤– Generated with Claude Code

https://claude.ai/code/session_01MjXPsBTaL6WV9AhCH2ajuv


Generated by Claude Code