Temporary diagnostic for #2267 — exists only to make CI run one test and be closed.
The two gateway.test.ts CLI cases hang on GitHub's Linux runners and nowhere else I can get to (not in oven/bun:1 on either arch under any configuration). Meanwhile cli.test.ts spawns the identical CLI via spawnSync and passes in the same run, so the entry point itself is fine.
zz-2267-diagnostic.test.ts runs eight spawn variants of bun bin/cli.ts --help from a parent that has the rpx graph loaded, with a 12s budget each, and dumps the stuck child's /proc state (status, wchan, kernel stacks via sudo -n, fds, cwd, children, io) before killing it. Every line is prefixed [2267-diag].
| variant | isolates |
|---|---|
G bun --version, node spawn | is it spawning bun at all, or the CLI graph? |
A cli --help, node spawn ['ignore','pipe','pipe'] | the exact failing shape (baseline) |
B A + BUN_RUNTIME_TRANSPILER_CACHE_PATH=0 | transpiler-cache contention |
C A + stdin pipe (ended) | stdin-ignore |
F A + cwd=tmpdir | repo-root bunfig.toml / cwd |
I A + stdout/stderr inherit | pipe plumbing vs child not running |
D Bun.spawn | the node:child_process shim specifically |
E spawnSync, parent has graph | cli.test.ts's shape, but with the graph loaded |
The test always passes; the log is the result. Will close once read.
🤖 Generated with Claude Code