Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cmd/go: report flaky failures #48027

jayconrod opened this issue Aug 27, 2021 · 0 comments

cmd/go: report flaky failures #48027

jayconrod opened this issue Aug 27, 2021 · 0 comments
fuzz NeedsFix


Copy link

@jayconrod jayconrod commented Aug 27, 2021

If the fuzz function finds an error for a given input while fuzzing, and the fuzz function finds no error when called again with the same input, go test -fuzz should report that the failure is "flaky".

As of CL 342996, the fuzzing engine will abandon an attempt to minimize the crash if it can't reproduce it. It will still record the unminimized input and exit non-zero though. We should keep doing that. However, the user may find that the crash does not reproduce, delete the input from testdata, then continue instead of investigating the flake.

@jayconrod jayconrod added NeedsFix fuzz labels Aug 27, 2021
@jayconrod jayconrod added this to the Go1.18 milestone Aug 27, 2021
@rsc rsc changed the title [dev.fuzz] cmd/go: report flaky failures cmd/go: report flaky failures Sep 21, 2021
@katiehockman katiehockman removed this from the Go1.18 milestone Nov 10, 2021
@katiehockman katiehockman added this to the Backlog milestone Nov 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
fuzz NeedsFix
None yet

No branches or pull requests

2 participants