fix: give the spinning-shard kill test load headroom (30s -> 90s)

The test spawns and group-kills three real children (one a busy-loop
burning a full core) while five sibling shard processes compete for eight
vCPUs. Under full-suite load it blew bun's default 30s per-test ceiling at
30,009ms — while passing in isolation in 1.4s — and red the only required
lane. Every assertion in it is event-based (statuses, group-kill proof,
heartbeat lines); the sole latency claim is the <30s kill-deadline sanity
bound, which stays. Explicit 90s headroom, not a weakened oracle.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Garry Tan
2026-08-31 04:06:35 +00:00
co-authored by Claude Fable 5
parent 0bbce3ea58
commit d96027c098
+7 -1
View File
@@ -159,7 +159,13 @@ describe('shard execution', () => {
expect(lines.filter((l) => l.includes(' START ')).length).toBe(3);
expect(lines.some((l) => /TIMED-OUT in \d+s/.test(l))).toBe(true);
expect(lines.some((l) => /PASSED in \d+s/.test(l))).toBe(true);
}, 30_000);
// 90s, not the default 30s: this test spawns/kills three real children
// (one a busy-loop burning a full core) while 5 sibling shard processes
// compete for 8 vCPUs — observed blowing exactly the 30s ceiling at
// 30009ms under full-suite load while passing in isolation in 1.4s.
// Every assertion above is event-based; the only latency claim is the
// <30s kill-deadline sanity bound, which stays.
}, 90_000);
test('exit 0 WITHOUT the terminal summary is FAILED — enforced for injected commands too', async () => {
// The invisible-non-execution backstop: previously the paid runner