[Fuzzing] Do not clusterfuzz multibyte#8488
Merged
Merged
Conversation
brendandahl
approved these changes
Mar 18, 2026
Collaborator
|
Should I have hit this issue locally when running |
Member
Author
|
It's hard to hit this locally because the fuzzer would need to get lucky and pick a multibyte testcase, and we run the ClusterFuzz fuzzer at low frequency. I guess it just took many days to find... |
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.
ClusterFuzz fuzzer in fuzz_opt.py hit this.
Also add fp16 in fuzz_opt.py for overall consistency, but fp16 is disabled
more generally there as well, a few lines above anyhow.