Repository navigation
Run CI tests with a 20 s default timeout - #2000
Merged
Merged
Conversation
…changelog] The first test loads the full shell bundle in real Chromium; on a loaded CI runner it passes Bun's 5 s default and the remaining tests cascade. It failed this way on #1995, #1996, #1998 and #1999 while passing on beta and #1997. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RwsemkhoUGyeQkdkKFmUmw
This was referenced Oct 20, 2026
Noisemaker111
enabled auto-merge
October 20, 2026 14:19
… [skip changelog] After the settings boundary test got 20 s, the same runner timed out hudInputBoundary and the Rapier slope test instead: whichever cold-start browser/WASM suite runs first under load passes Bun's 5 s default. All pass locally. Set the default for the CI test command; tests with their own timeout keep it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RwsemkhoUGyeQkdkKFmUmw
Noisemaker111
changed the title
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
2 participants
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.
#1995, #1996, #1998 and #1999 failed
testwith five failures insettingsBoundary.test.ts, while beta and #1997 passed..github/workflows/ci.yml:bun test --timeout 20000 packages apps/dev scripts. Tests that set their own timeout keep it.Root cause: suites that cold-start Chromium or Rapier WASM can run their first test past Bun's 5 s default on a loaded runner ("a beforeEach/afterEach hook timed out", ~5003 ms), and the rest of that file cascades. The first push here raised only
settingsBoundary's timeout; that file then passed, and the same run timed outhudInputBoundaryand the Rapier slope test instead. So the default is raised for the whole CI run and the per-file change is reverted.Verification
settingsBoundary5/5,hudInputBoundary5/5,characterMovement.rapier6/6, three runs);ship:preflight— okNo rendered surface changed.
🤖 Generated with Claude Code
https://claude.ai/code/session_01RwsemkhoUGyeQkdkKFmUmw