chore: Increase Yarn network timeout #5106
Merged
Conversation
This file contains 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
mwest1066
approved these changes
Nov 19, 2021
|
From a spot-check of the |
|
@mwest1066 the hypothesis from nodejs/docker-node#1335 is that "emulation is slow" which increases our likelihood of running into timeouts. Which seems plausible, but the default timeout is 30s, which already seems quite high, so 🤷 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This is a followup to #5105 that tries to fix the new build failures on master by increasing the Yarn timeout. If this doesn't work, we may have to switch to Yarn 2.