fix(dep-graph): set the number of workers with environment variables #8671
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
In a docker container, the result of os.cpus() can be wrong (nodejs/node#28762).
Nx Cloud ReportCI is running for commit 6affbee. 📂 Click to track the progress, see the status, the terminal output, and the build insights. Sent with 💌 from NxCloud. |
|
Thank you! Merged it here: b86feb1 |
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
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.
With docker, the result of os.cpus() can be wrong (nodejs/node#28762). In my company CI, it's lead to random failure with error 137.
Current Behavior
In my company we have a server with 64 cores to run our build pipline, but when we run the container with the limit of 4 cores, os.cpus().length return 64 instead 4.
It's a known issue in node.js nodejs/node#28762.
Expected Behavior
Run only the right number of workers.