cmd/go: fuzz corpus files should end in newline #48130
Labels
FrozenDueToAge
fuzz
Issues related to native fuzzing support
NeedsFix
The path to resolution is known, but the work has not been done.
release-blocker
Milestone
The corpus files written by go test -fuzz look like:
it's a great format, but what you can't see above is that they have no final \n on the last line. They should.
/cc @jayconrod @katiehockman
The text was updated successfully, but these errors were encountered: