[dev.fuzz] cmd/go: fuzzer output buffered/missing when testing a sub package #47603
Labels
FrozenDueToAge
fuzz
Issues related to native fuzzing support
NeedsFix
The path to resolution is known, but the work has not been done.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
n/a
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
In #fuzzing over in the gopher slack, @benhoyt reported that a fuzzer didn't give output. I made a minimal setup to reproduce the problem at https://github.com/stevenjohnstone/silent-beta-fuzz.
If you run the fuzzer outside of the package under test by specifying the package path, the output is lost.
What did you expect to see?
The usual output every 3 seconds
What did you see instead?
No output
The text was updated successfully, but these errors were encountered: