Limit fuzz builds in CI to 8 parallel tasks #3970
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
|
👋 Thanks for assigning @tnull as a reviewer! |
`cargo` can get excited seeing it has many available cores and will happily spawn core-count `ld` processes to link all the fuzzing binaries, using substantial very-short-term memory. This can cause issues in CI runners with many cores but not a ton of memory (eg 32 cores and only 16GiB of memory available).
TheBlueMatt
force-pushed
the
2025-07-less-fuzzing-mem
branch
from
906744c to
db4890d
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3970 +/- ##
=======================================
Coverage 88.92% 88.92%
=======================================
Files 174 174
Lines 123869 123869
Branches 123869 123869
=======================================
+ Hits 110152 110156 +4
+ Misses 11256 11255 -1
+ Partials 2461 2458 -3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
👋 The first review has been submitted! Do you think this PR is ready for a second reviewer? If so, click here to assign a second reviewer. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
cargocan get excited seeing it has many available cores and will happily spawn core-countldprocesses to link all the fuzzing binaries, using substantial very-short-term memory. This can cause issues in CI runners with many cores but not a ton of memory (eg 32 cores and only 16GiB of memory available).