internal/fuzz: internal panics are reported as unexpected crashes and written to testdata #48804
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
There are a few things that could go wrong in the worker that we know is our fault, so we panic in those situations. For example: https://cs.opensource.google/go/go/+/e213c72fb9492a409bd0ed9620ca9aaaa96ddebe:src/internal/fuzz/worker.go;l=691;bpv=1
However, in playing around locally, it looks like if a panic like this occurs, then we just end up printing something like this:
First of all, the panic text is lost, so the developer has no idea what went wrong.
Secondly, it writes the crash to testdata even though we already know this is a bug in our code, so we shouldn't do that.
/cc @golang/fuzzing
The text was updated successfully, but these errors were encountered: