rabbitblood 5478beef90 fix(canary): bump job timeout to 25m so bash fail + diagnostic can fire (#2090) ... PR #2107 bumped the bash-side TLS-readiness deadline in tests/e2e/test_staging_full_saas.sh from 600s to 900s (15 min) AND added a diagnostic burst on the fail path so the next failure would identify the broken layer (DNS / TLS / HTTP). What I missed: the canary workflow's own timeout-minutes was also 15. So GitHub Actions killed the job at the 15:00 wall-clock mark BEFORE the bash `fail` + diagnostic could fire — every cancellation silent, no failure comment on #2090, no diagnostic data attached. Visible in the 21:03 UTC canary run: cancelled at 14:03 step time (15:18 wall) without ever reaching the diagnostic block. Bump to 25 min — gives ~10 min headroom over the 15-min bash deadline for setup (org create + tenant provision + admin token fetch) plus the diagnostic dump plus teardown. Still tighter than the sibling staging E2E jobs (20/40/45 min) so a genuine wedge surfaces here first. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-26 14:36:02 -07:00
..
workflows	fix(canary): bump job timeout to 25m so bash fail + diagnostic can fire (#2090)	2026-04-26 14:36:02 -07:00
CODEOWNERS	chore: add CODEOWNERS to auto-route agent PRs to personal review account	2026-04-26 13:40:13 -07:00