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

Jump to bottom

cmd/go: use testdata/fuzz not testdata/corpus for fuzzing #48128

Closed
rsc opened this issue Sep 2, 2021 · 2 comments
Closed

cmd/go: use testdata/fuzz not testdata/corpus for fuzzing #48128

rsc opened this issue Sep 2, 2021 · 2 comments
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
Go1.18

Comments

@rsc
Copy link
Contributor

rsc commented Sep 2, 2021

Fuzzing support writes to testdata/corpus. Other tests might have other kinds of corpora already, and we might step on it a bit. It would be better to give it a name specific to fuzzing. I suggest testdata/fuzz.
@rsc rsc added NeedsFix The path to resolution is known, but the work has not been done. release-blocker labels Sep 2, 2021
@rsc rsc added this to the Go1.18 milestone Sep 2, 2021
@rsc
Copy link
Contributor Author

rsc commented Sep 2, 2021

/cc @jayconrod @katiehockman

@jayconrod jayconrod added the fuzz Issues related to native fuzzing support label Sep 9, 2021
@katiehockman katiehockman self-assigned this Sep 10, 2021
@gopherbot
Copy link

Change https://golang.org/cl/349053 mentions this issue: [dev.fuzz] testing: move corpus from testdata/corpus to testdata/fuzz

gopherbot pushed a commit that referenced this issue Sep 10, 2021
@katiehockman
[dev.fuzz] testing: move corpus from testdata/corpus to testdata/fuzz
b38e853 
Fixes #48128

Change-Id: I04deb17226ff5d5dfcbe408fe089f400d4d3836f
Reviewed-on: https://go-review.googlesource.com/c/go/+/349053
Trust: Katie Hockman <katie@golang.org>
Run-TryBot: Katie Hockman <katie@golang.org>
TryBot-Result: Go Bot <gobot@golang.org>
Reviewed-by: Jay Conrod <jayconrod@google.com>
@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.
Assignees
No one assigned
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
Projects
Go Security
Status: No status
Milestone
Go1.18
Development

No branches or pull requests
4 participants
@rsc @jayconrod @gopherbot @katiehockman