3 people ee1450b5d4 test: bound every test process registry by the running test ...

Registries created directly with createTestProcessRegistry did not get the
processTest default, so a hung child there had no deadline once its explicit
value was removed; Vitest's test timeout does not settle the awaited run, so
shutdown was never reached. Derive the default in the registry from the
running test instead, using the real clock.

Co-Authored-By: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-11-14 13:21:13 +08:00

..

observePosixProcess.ts

test(apktool): own lifecycle fixtures and process observations

2026-10-23 18:40:23 +08:00

pidFile.ts

fix(test): wait for valid debugger fixture PIDs (#9208)

2026-11-07 11:12:43 +08:00

processFixture.ts

test: bound every test process registry by the running test

2026-11-14 13:21:13 +08:00

spawnArgumentLimit.ts

test(cli): keep IPC trace input under the Linux spawn limit (#5673)

2026-10-21 04:48:33 +08:00