forked from molecule-ai/molecule-core
5478beef90
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> |
||
|---|---|---|
| .. | ||
| auto-promote-staging.yml | ||
| auto-tag-runtime.yml | ||
| block-internal-paths.yml | ||
| canary-staging.yml | ||
| canary-verify.yml | ||
| check-merge-group-trigger.yml | ||
| ci.yml | ||
| codeql.yml | ||
| e2e-api.yml | ||
| e2e-staging-canvas.yml | ||
| e2e-staging-saas.yml | ||
| e2e-staging-sanity.yml | ||
| promote-latest.yml | ||
| publish-canvas-image.yml | ||
| publish-runtime.yml | ||
| publish-workspace-server-image.yml | ||
| redeploy-tenants-on-main.yml | ||
| retarget-main-to-staging.yml | ||
| runtime-pin-compat.yml | ||
| secret-scan.yml | ||
| sweep-cf-orphans.yml | ||
| sweep-stale-e2e-orgs.yml | ||
| test-ops-scripts.yml | ||