[INTERNAL] Increase AVA test timeouts - #1237
Merged
Merged
Conversation
matz3
approved these changes
Sep 16, 2026
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
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.
AVA's default inactivity timeout is 10 seconds — the timer resets on every test event and fires if the runner is silent for longer than that window.
The test suite in
test/lib/builder/builder.jsincludes integration-style builds that process full project graphs. On slower CI machines these builds can silently exceed 10 s between test events, causing AVA to forcibly exit the worker process and report all remaining serial tests in that file as "timed out / pending."Setting "timeout": "2m" gives each quiet window enough headroom for a slow build pass without masking genuinely hung tests.
More about AVA timeouts: https://github.com/avajs/ava/blob/bbfd946322fdeca2b547a691d947fb4e18c0c67f/docs/07-test-timeouts.md