The run on main (commit 91646ae2) failed in the test job; all five platform builds passed. One test failed:
(fail) Claude Code here runs out of the terminal's process group: Ctrl-C reaches Obeya alone,
which ends it and what it runs as it stops
src/server/runtime.test.ts:242 expect(() => process.kill(-Number(group), 0)).toThrow()
Received function did not throw
The test starts an agent that runs a command, sends the group SIGTERM and, as soon as the agent has exited, checks that nothing of its process group is left. The command has the signal by then, but it can still be there for a moment, until it has exited and been reaped. On a busy CI runner that moment is sometimes long enough for the check. Obeya's own code works as intended. The next run on main (39610956649) passed with the same code.
The test now waits up to two seconds for the process group to go, and only then checks it. If the command is really left running (it sleeps for 30 s), the test still fails as before.
| Fixed test, 15 runs in a row | 15 pass |
| Full suite | 0 fail |
| Typecheck | clean |
An earlier failed run (39601318777) had a different flaky test, in the Koordinator's brief. It is left to a card of its own.