mise run test runs the Deno/Node.js/Bun suites in parallel and saturates the CPU. Under that load, packages/cli/src/startup.test.ts (which spawns a node dist/mod.js --help subprocess) exceeds Bun's default 5000ms per-test timeout and is killed, failing with null !== 0 "Unhandled error between tests". It never fails under mise run test:bun alone.
The cause is that cli's test:bun script has no explicit --timeout, unlike most packages (fedify, postgres, redis, sqlite, … all pass one). The same is missing in debugger and vocab-tools.
Proposed Fix
Add an explicit --timeout to the test:bun scripts of cli, debugger, and vocab-tools, consistent with the rest of the monorepo:
- "test:bun": "bun test"
+ "test:bun": "bun test --timeout 60000"
Test-infrastructure only; no product code changes.
Note
Observed on a branch based on 2.0-maintenance, so the missing --timeout may already be addressed on main or other branches.
mise run testruns the Deno/Node.js/Bun suites in parallel and saturates the CPU. Under that load,packages/cli/src/startup.test.ts(which spawns anode dist/mod.js --helpsubprocess) exceeds Bun's default 5000ms per-test timeout and is killed, failing withnull !== 0"Unhandled error between tests". It never fails undermise run test:bunalone.The cause is that
cli'stest:bunscript has no explicit--timeout, unlike most packages (fedify,postgres,redis,sqlite, … all pass one). The same is missing indebuggerandvocab-tools.Proposed Fix
Add an explicit
--timeoutto thetest:bunscripts ofcli,debugger, andvocab-tools, consistent with the rest of the monorepo:Test-infrastructure only; no product code changes.
Note
Observed on a branch based on
2.0-maintenance, so the missing--timeoutmay already be addressed onmainor other branches.