ci: drop fuzz per-target time 60s -> 15s#24
Merged
Conversation
Post-merge fuzz on main is currently the longest job in the pipeline at ~10 minutes (10 targets x 60s). 15s per target keeps the smoke-test intent - crashes from the seed corpus surface in the first few seconds - while bringing total runtime to ~3 min and cutting runner-minute spend by ~4x. Co-Authored-By: Claude
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
1 participant
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.
Summary
Cuts the fuzz
-max_total_timefrom 60s to 15s per target. Post-merge fuzz on main goes from ~10 min total to ~3 min, roughly 4x fewer runner-minutes per push.15s per target is still enough to catch crashes that surface from the existing seed corpus; deeper campaigns belong off-CI anyway.
Test plan