SYM-41: Raise bun test per-test timeout to 30s#9
Open
Swiftyos wants to merge 1 commit into
Open
Conversation
Subprocess-heavy e2e tests (CLI boot, SIGTERM handshake, multi-command openclaw flows, report rendering) regularly approach Bun's default 5 s per-test limit on loaded local workspaces while CI passes. The harness already caps each child subprocess at 30 s internally (assertProcessCompletes in tests/e2e/support.ts), so aligning Bun's per-test timeout with that watchdog stops false timeouts without masking real hangs. Co-Authored-By: Claude Opus 4.7 (1M context) <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
tests/e2e/support.ts:144), fixing localbun run fast-feedbackflakes where subprocess-heavy e2e tests (CLI boot/SIGTERM, openclaw multi-command flows, run+report rendering) crossed Bun's 5 s default.assertProcessCompletesstill kills any child subprocess at 30 s, so a genuinely hung test still fails with a clear subprocess kill rather than a Bun timer race.package.jsontest/test:e2escripts; no code or harness changes.Root cause
On a clean workspace (
bun installfresh) the full e2e file ran in 7.6–9.0 s wall time. The slowest individual test (run records the suite in sqlite and report renders both explicit and discovered outputs) was 3.4 s isolated — close enough to 5 s that normal workspace load pushes it over. The ticket reported ~5.1 s for that exact test. CI runs on lightly loaded runners and has stayed green; only loaded local workspaces tripped the limit.Test plan
bun installon a clean workspacebun run fast-feedbackpasses locally (docs, lint, typecheck, 51 tests in 13.7 s)bun test tests/e2eruns all greenCloses SYM-41.
🤖 Generated with Claude Code