-
Notifications
You must be signed in to change notification settings - Fork 18k
internal/fuzz: enable fuzz testing on OpenBSD #60491
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
Comments
cc @golang/openbsd |
This change provides support for -fuzz flag on OpenBSD. According to golang#46554 flag was unsupported because of lack of testing on all OSes. Fixes: golang#60491
|
This change provides support for -fuzz flag on OpenBSD. According to golang#46554 the flag was unsupported because of lack of proper testing on all OSes. Fixes: golang#60491
This change provides support for -fuzz flag on OpenBSD. According to golang#46554 the flag was unsupported on some OSes due to lack of proper testing. Fixes: golang#60491
This change provides support for -fuzz flag on OpenBSD. According to golang#46554 the flag was unsupported on some OSes due to lack of proper testing. Fixes: golang#60491
Change https://go.dev/cl/499335 mentions this issue: |
I also needed to sign CLA and change email in commit from github private to the same as in CLA. |
This will need to wait until the development window reopens after the release of Go 1.21. |
Go 1.21 has passed, but https://go.dev/cl/499335 remains on hold. What's the reason for the delay? |
It would be good to mention this in Go 1.25 release notes (#71661), otherwise users may not know about it. See doc/README.md. |
On current version of OpenBSD you cannot run fuzz tests:
It looks like artificial restriction (comment by @dr2chase in #46554 (comment)):
After extending
platform.FuzzSupported(goos, goarch string)
and build tags insidesrc/internal/fuzz/
directory, I can runall.bash
with success and use newly built executable to run fuzz tests.I've read contribution rules, but I'm not sure what should I do next. Is it enough to create pull request with this change?
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
I suppose
The text was updated successfully, but these errors were encountered: