Update CI mode script to allow passing in args#421
Draft
GyozaGuy wants to merge 2 commits intofrontierMasterfrom
Draft
Update CI mode script to allow passing in args#421GyozaGuy wants to merge 2 commits intofrontierMasterfrom
GyozaGuy wants to merge 2 commits intofrontierMasterfrom
Conversation
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.
On Linux systems, running Jest tests with the default options can consume all system memory and cause the operating system to crash. Being able to specify how many workers are used makes a huge difference in system stability.
This was tested by manually modifying this script in my
node_modulesdirectory and running tests in CI mode with the--maxWorkers=2option passed in.In Jest 29 we would be able to use the
JEST_MAX_WORKERSenvironment variable, but since we're still on Jest 27 we don't have this option.