Skip to content

fix(test): raise tree-sitter WASM init timeout for slow CI runners #2015

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
gfargo-horizon-agent wants to merge 1 commit into from
Closed

fix(test): raise tree-sitter WASM init timeout for slow CI runners #2015

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions src/lib/parsers/default/__tree_sitter__/tsTreeSitterParser.test.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,12 @@ describeWithWasm('treeSitterTsParser (.wasm-backed)', () => {
// race the init promise. The init failure path is now retry-friendly
// (see `ensureRuntime` in runtime.ts), and we trust the first test in
// this suite to exercise the init path cleanly.
//
// The one-time `Parser.init` WASM bootstrap can exceed jest's default
// 5000ms on a loaded/slow CI runner (observed on macOS runners); bump
// the suite timeout so a slow cold start doesn't fail an otherwise
// passing assertion.
jest.setTimeout(20000)

it('returns undefined for non-TS / non-JS file paths', async () => {
expect(await treeSitterTsParser.summarize(fileDiff('README.md', '+x'))).toBeUndefined()
Expand Down
Loading