scanbuild: obey MESON_NUM_PROCESSES environment variable #15094
Merged
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
|
Example job that is OOMs because scan-build uses 64 threads from the CPU instead of the available 8 in the runner: https://gitlab.desy.de/constellation/constellation/-/jobs/982477 ( |
|
@bonzini I'm not sure if there is a 1.8.6 release planned to be included in Fedora 43, but this would be a good addition for such a release. |
|
@stephanlachnit Can you rebase this, that should resolve the red CI |
stephanlachnit
force-pushed
the
p-scan-build-num-processes
branch
from
2435501 to
063458a
Compare
@dcbaker done! |
dcbaker
approved these changes
Oct 9, 2025
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.
When using scan-build, it uses all threads by default. In cloud environments where the exposed number of cores by system might not be the same as the available cores, this can be a problem leading to OOM.
The simple fix is adding the number of cores via
-jto the ninja invocation using thedetermine_worker_countfunction.