fix(test): raise tree-sitter WASM init timeout for slow CI runners - #2015
Closed
gfargo-horizon-agent[bot] wants to merge 1 commit into
Closed
fix(test): raise tree-sitter WASM init timeout for slow CI runners#2015gfargo-horizon-agent[bot] wants to merge 1 commit into
gfargo-horizon-agent[bot] wants to merge 1 commit into
Conversation
The `.wasm-backed` tree-sitter parser suite pays the one-time `Parser.init` bootstrap cost on its first real test. Jest's default 5000ms budget was tight enough that the macOS CI runner (Node 22.22.2) intermittently exceeded it, unrelated to the runner's own logic. Bump the suite timeout to 20000ms to absorb cold-start variance.
Owner
|
Superseded by #2023 which applies the same fix in a more targeted way (per-test timeout). |
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.
What
Bumps the
.wasm-backedtree-sitter parser suite's jest timeout to 20000ms.Why
Split out of #1983 (
coco watch) per review feedback — this fix is unrelated to that feature and was flagged as unrelated bundling across three review rounds.The
.wasm-backedtree-sitter parser suite pays the one-timeParser.initbootstrap cost on its first real test. Jest's default 5000ms budget was tight enough that the macOS CI runner (Node 22.22.2) intermittently exceeded it, unrelated to the runner's own logic.How
jest.setTimeout(20000)in the WASM-backed parser test suiteTesting
🤖 Generated by the harbor agent loop. Reviewed by a human before merge.