[infra] Match workers and jobs per core #13102
Open
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
JarLob
force-pushed
the
parallel
branch
2 times, most recently
from
46155e7 to
652750a
Compare
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.
Although the
parallel-fuzzinginput parameter is documentedto use all available cores for fuzzingit is not how it currently works because as it is written in libfuzzer documentationThese jobs will be run across a set of worker processes, by default using half of the available CPU cores;I.e. currently when
parallel-fuzzingis set totrueit uses for example 1 core on a 2 cores machine.The PR makes jobs number always match the workers number. Additionally a user may specify the number of cores to use manually.