dev: get rid of fuzzing stubs#67675
Merged
Merged
Conversation
I don't think anyone actually uses fuzzing and it doesn't seem to be a requirement for `dev`. Until such a point as we actually need it for something, remove these stubs. Release note: None
Member
|
This change is |
rail
approved these changes
Jul 15, 2021
rail
left a comment
Member
There was a problem hiding this comment.
Reviewed 1 of 1 files at r1.
Reviewable status:complete! 1 of 0 LGTMs obtained (waiting on @rickystewart)
Contributor
Author
|
bors r=rail |
Contributor
|
Build succeeded: |
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
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.
I don't think anyone actually uses fuzzing and it doesn't seem to be a
requirement for
dev. Until such a point as we actually need it forsomething, remove these stubs.
Release note: None