Set default NUM_JOBS value to be the same accross all scripts #1688
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
valentinThomazic
requested review from
JeanRochCoulon and
zarubaf
as code owners
|
✔️ successful run, report available here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
NUM_JOBSvalue inverif/regress/install-cva6.pywhich defeated the purpose of settingNUM_JOBSand could have potentially resulted in issues on some system configurations, since it was set quite high.NUM_JOBSvalue to 1 in all scripts.An unset
NUM_JOBSenvironment variable should now results in a sequential execution of make jobs in all scripts, as described in theREADME's Quickstart