Skip to content

test: give envelope spawn-loop tests timeout headroom - #65

Merged
yusukebe merged 1 commit into
mainfrom
test/cli-loop-timeouts
Aug 4, 2026
Merged

test: give envelope spawn-loop tests timeout headroom#65
yusukebe merged 1 commit into
mainfrom
test/cli-loop-timeouts

Conversation

@yusukebe

@yusukebe yusukebe commented Aug 4, 2026

Copy link
Copy Markdown
Owner

Summary

  • add explicit 30s timeouts to the two --json-envelope continuation-loop tests in test/cli.test.ts

Why

Same class as #58, other file: each loop spawns bun+ax ~10 times, and under machine load (reproduced locally at load average ~6.5, where the whole suite slows 6x) the total exceeds Bun's default 5s per-test timeout — json envelope: budget continuation reconstructs the full result failed with a timeout + JSON parse EOF from the killed spawn, including when run in isolation. ci.yml runs on 2-core runners, so the same flake is reachable there.

With the headroom both tests pass under the same load. No behavior under test is changed.

🤖 Generated with Claude Code

The two continuation-loop tests spawn ax ~10 times each; under machine
load that exceeds Bun's default 5s test timeout (reproduced at load
average ~6.5, including in isolation). Same fix as the bench tests in #58.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@yusukebe
yusukebe merged commit 2cafec1 into main Aug 4, 2026
1 check passed
yusukebe added a commit that referenced this pull request Aug 4, 2026
Third round of the same flake: after #58 (bench) and #65 (cli envelope
loops), yet another spawn-heavy bench test breached Bun's 5s default under
machine load. The suite spawns bun+ax subprocesses by design, so stop
playing whack-a-mole per test and raise the default via bun test --timeout
in the test script and CI. (bunfig [test].timeout is not honored — verified.)

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant