Julian Sommer 4522494c17 fix: define the per-suite e2e test timeout once, in suite-sets.sh ...

The timeout was written out separately in each workflow and drifted: rds
ran 50m on the PR gate and 30m nightly, where it panicked and took six
in-flight subtests with it. e2e-suites.yml had the same hardcoded 30m on
its single path, which also runs rds.

A new e2e_suite_timeout helper sits beside the eligibility lists it
already guards, and all four call sites resolve through it. e2e.yml loops
over suites on the remote VM, which has no checkout, so it resolves the
pairs on the runner and looks them up in the loop.

Also lift the nightly cell ceiling to 50 minutes so the rds cell is not
cut short by the job before its own timeout applies.

2026-09-03 09:21:17 +10:00

..

capture-net-diag.sh

fix(network): IGW route-table AWS parity + per-subnet egress gating (#270)

2026-06-01 09:54:29 +10:00

ci-fmt.sh

feat(e2e): Go E2E harness + single-node migration to Ensure*/Discover* + reboot suite (#241)

2026-05-20 21:04:13 +10:00

ensure-libguestfs.sh

ci: run eks, ecs and rds nightly in dedicated cells (#984)

2026-09-02 16:16:05 +10:00

start-net-capture.sh

fix(network): IGW route-table AWS parity + per-subnet egress gating (#270)

2026-06-01 09:54:29 +10:00

suite-sets.sh

fix: define the per-suite e2e test timeout once, in suite-sets.sh

2026-09-03 09:21:17 +10:00