Compare commits

..
Author SHA1 Message Date
Brent Vatne 7d75093062 exec: de-flake the SIGKILL escalation test
The test spawned a node child that installed a SIGTERM handler and relied on
a 250ms deadline to fire after it. The deadline timer starts at spawn, so on a
loaded runner node had not yet reached `process.on('SIGTERM')` when the signal
landed: the default disposition killed it outright, the 5s grace-timer
escalation never ran, and the elapsed-time assertion saw 462ms. That failed
the v0.10.0 release job before the publish step.

Use `sh -c 'trap "" TERM; exec sleep 30'` instead. The shell boots in ~1ms
rather than a node runtime's tens of ms, and an ignored signal survives exec
where an installed handler would not, so the sleep holding the group ignores
SIGTERM too. Widen the deadline to 1s as well, so the window the child has to
get there is 4x larger.
2026-08-05 14:38:17 -07:00
Brent Vatne b5466193b6 runtime: stream Claude agent activity (#58) 2026-08-04 21:39:03 -07:00
+15 -9
View File
@@ -71,17 +71,23 @@ test("run with input: timeout kills the whole process group, not just the direct
test("run with input: escalates to SIGKILL after the grace period when the child traps SIGTERM", async () => {
const started = Date.now();
const result = await run(
"node",
["-e", "process.on('SIGTERM', () => {}); setInterval(() => {}, 1000);"],
{ input: "", timeout: 250, check: true },
);
// The deadline timer starts at spawn, so the child must have SIGTERM ignored
// before it fires or the default disposition kills it and this never reaches
// the escalation path. `sh` with an ignoring `trap` is the cheapest way there:
// it boots in ~1ms (a node runtime takes far longer, and lost this race on a
// loaded CI runner), and an *ignored* signal survives `exec` where an
// installed handler would not — so the `sleep` holding the group ignores it too.
const result = await run("sh", ["-c", 'trap "" TERM; exec sleep 30'], {
input: "",
timeout: 1000,
check: true,
});
expect(result.timedOut).toBe(true);
// SIGTERM alone never ends a process that traps it; only the 5s grace-timer
// SIGTERM alone never ends a process that ignores it; only the 5s grace-timer
// SIGKILL escalation does, so a duration past that proves the path fired.
expect(Date.now() - started).toBeGreaterThanOrEqual(5000);
expect(Date.now() - started).toBeLessThan(10_000);
}, 10_000);
expect(Date.now() - started).toBeGreaterThanOrEqual(6000);
expect(Date.now() - started).toBeLessThan(14_000);
}, 20_000);
test("run without input: timeout resolves timedOut too (execFile path, same contract)", async () => {
const started = Date.now();