fix: Increase timeout for npm-webpack-dev-server tests #22489
Merged
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.
User facing changelog
No user facing changes.
Additional details
The system tests in
sourceRelativeWebpackModules.spec.ts
have been extremely flaky the past few days, to the point where it's more "consistent failure" than it is "flake".It seems to be simply a timeout issue - the 10s we've allocated aren't enough to successfully yarn install all the dependencies for
webpack5_wds4-react
and similar system test projects.While I'd very much like to rewrite these tests so as not to take so long, there's no quick solution here and it would probably involve changing how we install system test dependencies entirely (or mocking them out not to actually install), something beyond the scope of my efforts at the moment.
Therefore, timeout increase. Green builds are super important.
Steps to test
How has the user experience changed?
PR Tasks
cypress-documentation
?type definitions
?