test: increase ref2vaWrapper cancellation test timeouts for full-suite load (#9055) - #9060
Merged
Merged
Conversation
…e load (#9055) The test spawns child processes with three sequential waitFor stages, each with 5s timeouts. Under full-suite load (2500+ files), the first stage (waiting for the runtime pid file) exceeds 5s because Node cold start + wrapper startup + fake-runtime spawn competes for CPU. Increased only the first waitFor timeout from 5s to 10s for startup under load, kept others at 5s to preserve the process-group-kill behavior test, and raised overall test timeout from 15s to 25s to provide headroom. This remains load-sensitive but deterministic.
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
Fixed a load-sensitive flake in
ref2vaWrapper.test.jsby increasing only the startup-stage timeout from 5s to 10s. The test spawns child processes with three sequentialvi.waitForstages; under full-suite load (2500+ files), the first stage (waiting for the runtime pid file to be written) exceeds 5s due to CPU contention during Node cold start + wrapper initialization + fake-runtime spawn.vi.waitFortimeout from 5s → 10s for startup under loadTest plan
Closes #9055