[lavaman131]

The connector test "a run behind a gateway answering 502 with no body says HTTP 502 while it retries" failed on unrelated PRs. In one run it printed attempt 6, 28 s where it expected attempt 6, 24 s. In another, the attempt 6 line never appeared. Locally it passed.

Cause

The fake gateway moved the test's clock four seconds for every refused request and ended the outage after eight. The test expected all eight to come from the heartbeat. But the agent sends its session report (report_implementation_build, state running) when it starts. On a fast runner, that report arrived during the outage. Each of its retries registered the machine again and was refused, which moved the clock and used up one of the eight refusals. The heartbeat then printed other attempt numbers and elapsed times, or the outage ended before its sixth attempt. Both CI failures fit one or two refusals of this kind.

The connector is not at fault here: a report retried during an outage should keep trying to reach Chopin.

Fix

This changes only the test. Chopin now goes away only once it has heard the agent's session report. After that, every refused request comes from the heartbeat, so the printed lines are the same on every run, and the exact assertions stay. The test now waits for the agent to start before the outage, so it takes longer and gets a 10 second budget, as other slow tests in the file do.

Evidence

• Before: with only the test process paused again and again (SIGSTOP 30 ms, then run 10 ms, which lets the agent start while the outage is still going), the old test failed 19 of 20 runs. One failure showed the exact CI mismatch: attempt 6, 28 s instead of attempt 6, 24 s.
• After, on the same test logic:
  • 50 plain runs: 50 passed.
  • 50 runs with the same pausing: 50 passed.
  • 20 runs with heavier pausing (stop 50 ms, run 5 ms): 20 passed.
  • 50 runs pinned to one CPU beside three busy loops: 50 passed. The slowest took 5.6 s, which is why the 10 second budget is needed.
• Before the 10 second budget was added, 1 of 50 pinned runs timed out at bun's default 5 s.
• bun test apps/connector, bun run types and bun run ci pass.