test: raise the suite-wide test timeout to 30s - #66
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
bun test --timeout 30000in both thepackage.jsontest script and ci.ymlWhy
Third round of the same flake class: after #58 (bench tests) and #65 (cli envelope loops), a different spawn-heavy bench test (
instrumented ax > resolves the shim, preserves output, and records each semicolon command) breached Bun's 5s default per-test timeout under machine load. This suite spawnsbun+ax subprocesses by design — CLI integration tests and the continuation bench — so per-test patches are whack-a-mole; the default is what's wrong for this repo.bunfig.toml [test] timeoutis not honored by bun 1.3/1.4 (verified empirically), so the flag it is. Full suite passes under the same load that reproduced the failure (270 pass). The per-test timeouts from #58/#65 stay — they're redundant now but harmless documentation of the hot spots.🤖 Generated with Claude Code