Skip to content

tests/fuzzers: move fuzzers into native packages #28411

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

Closed
wants to merge 6 commits into from

Conversation

holiman
Copy link
Contributor

@holiman holiman commented Oct 24, 2023

This PR moves our fuzzers from tests/fuzzers into whatever their respective 'native' package is.

The historical reason why they were placed in an external location, is that when they were based on go-fuzz, they could not be "hidden" via the _test.go prefix. So in order to shove them away from the go-ethereum "production code", they were put aside.

But now we've rewritten them to be based on golang testing, and thus can be brought back. More or less fully, there are still some workarounds required to get around AdamKorcz/go-118-fuzz-build#16 and https://github.com/AdamKorcz/go-118-fuzz-build#using-test-utils-from-other-_testgo-files .

This PR also adds a fuzzer for precompiled contracts, because why not.

Still WIP, there are more fuzzers to move.

Copy link
Member

@MariusVanDerWijden MariusVanDerWijden left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@holiman
Copy link
Contributor Author

holiman commented Nov 5, 2023

Superseded by #28467

@holiman holiman closed this Nov 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants