Group fuzz targets in fuzzing workflow#12450
Open
mattsu2020 wants to merge 2 commits into
Open
Conversation
This prevents false positives from the spell checker when encountering the `PIPESTATUS` environment variable in the fuzzing CI configuration.
Contributor
|
Is this intended to address #12446? |
Contributor
Author
It can be used as a mitigation measure. |
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.
What changed
should_passfiles.should_pass: trueexits unsuccessfully.Why
This reduces repeated setup overhead in the fuzzing workflow by cutting down the number of short-lived matrix jobs that each repeat checkout, cargo-fuzz installation, and toolchain setup.
Closes #12449.