Fix gitea's native fuzzers #9378
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
The fuzz targets were adapted to use Go's native fuzzing
kyakdan
force-pushed
the
fix-gitea-native-fuzzers
branch
from
4c0022b to
7617afc
Compare
The project now uses Go native fuzzing and the fuzz tests were moved into a dedicated `fuzz` package.
kyakdan
force-pushed
the
fix-gitea-native-fuzzers
branch
from
7617afc to
be5fb16
Compare
AdamKorcz
approved these changes
Jan 9, 2023
eamonnmcmanus
pushed a commit
to eamonnmcmanus/oss-fuzz
that referenced
this pull request
Mar 15, 2023
gitea's fuzz targets now use Go native fuzzing, and they were moved into a dedicated `fuzz` package (go-gitea/gitea#22376).
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.
gitea's fuzz targets now use Go native fuzzing, and they were moved into a dedicated
fuzzpackage (go-gitea/gitea#22376).