test: fix race condition in watch mode tests #61615
Open
+30
−12
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
Fixes race condition in watch mode tests that caused intermittent failures.
Problem
The watch mode tests using
runInBackground()had a race condition where the stdout "Failed running" message could arrive before stderr was fully collected, causing assertions on stderr content to fail with empty strings.Solution
When "Failed running" is detected in stdout and stderr is empty, wait for the stderr 'data' event before resolving the promise. This is an event-driven approach rather than timing-based.
Verification
test-watch-mode-restart-esm-loading-error.mjs: 200 runs, 0 failurestest-watch-mode.mjs: 50 runs, 0 failuresRefs: nodejs/reliability#1450