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: fuzz tests should use -count=1 where possible #48984

Closed
katiehockman opened this issue Oct 14, 2021 · 1 comment
Closed

cmd/go: fuzz tests should use -count=1 where possible #48984

katiehockman opened this issue Oct 14, 2021 · 1 comment
Labels
FrozenDueToAge fuzz Issues related to native fuzzing support NeedsFix The path to resolution is known, but the work has not been done. Testing An issue that has been verified to require only test changes, not just a test failure.
Milestone

Comments

@katiehockman
Copy link
Contributor

We have some hacks in our tests in order to make sure something is only printed once (e.g. https://cs.opensource.google/go/go/+/master:src/cmd/go/testdata/script/test_fuzz_chatty.txt;l=46?q=test_fuzz_ch&ss=go%2Fgo), but there is a much nicer way to do that. We can just use -count= in the stdout check line.

@katiehockman katiehockman added Testing An issue that has been verified to require only test changes, not just a test failure. NeedsFix The path to resolution is known, but the work has not been done. fuzz Issues related to native fuzzing support labels Oct 14, 2021
@katiehockman katiehockman added this to the Go1.18 milestone Oct 14, 2021
@gopherbot
Copy link

Change https://golang.org/cl/369674 mentions this issue: cmd/go: use -count=1 in test_fuzz_chatty.txt

@golang golang locked and limited conversation to collaborators Jun 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge fuzz Issues related to native fuzzing support NeedsFix The path to resolution is known, but the work has not been done. Testing An issue that has been verified to require only test changes, not just a test failure.
Projects
Status: No status
Development

No branches or pull requests

3 participants