joshsiv-mulga 760acd1eb4 test(e2e-lb): resolve peer availability before shared fixture setup ...

setupSharedFixture builds a VPC + 2 app VMs + probe client (minutes
on capacity-tight dev hosts) and previously ran BEFORE the peer
pickup + ssh.Ping. On single-node, the InternetFacing_* subtests
would correctly t.Skip on peer == "" — but only after the fixture
work and once subtests started, so the wait appeared to be attached
to the first subtest name gotestsum printed.

Reorder: pickPeer + ssh.Ping first, log "internet-facing will skip"
immediately, then build the fixture for the internal subtests.
No behavior change for multi-node + peer-reachable; on single-node
the skip rationale surfaces before the fixture wait.

2026-05-18 23:01:00 +10:00

..

testdata

feat(e2e): share probe client across both internal LB suites + SG fixes

2026-05-18 16:10:12 +10:00

lb_test.go

test(e2e-lb): resolve peer availability before shared fixture setup

2026-05-18 23:01:00 +10:00