Fix MesonNinja easyblock to avoid ninja using all CPUs when only 1 is requested#4023
Merged
boegel merged 2 commits intoeasybuilders:developfrom Dec 15, 2025
Merged
Conversation
ninja using all CPUs when only 1 is requestedMesonNinja easyblock to avoid ninja using all CPUs when only 1 is requested
Member
|
Test report by @boegel Overview of tested easyconfigs (in order)
Build succeeded for 3 out of 3 (total: 1 hour 59 mins 39 secs) (3 easyconfigs in total) |
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
2 participants
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.
Running
ninjawith no-joption will result in it using all available CPUs, which is the opposite of what one would want when running withmax_parallel = 1