-
Notifications
You must be signed in to change notification settings - Fork 14
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
Add Fuzzer tests for Evm.StepN #547
Conversation
12760dd
to
198620a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, looking forward to the presentation !! that said, I still have a couple of comments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, just a few minor requests for improvement.
2d207b4
to
5cfb2ce
Compare
414e117
to
530b4a2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good !! just a couple of sugestions/comments
After review changes, differential test found a new error in the lfvm: #547 |
- use min-newestSupported ops - fix issue with opcode range - document stack seed
fix real max stack size.
- use string builder instead of chain of concatenations - Rename humanreadablestring to Toxxxx to better reflect data transformation.
Co-authored-by: Facu <[email protected]>
Rename corpus input data to corpus entry like in manual
a87b31b
to
61b0b1f
Compare
113e0fc
This PR adds 3 fuzzer functions for the ct Evm.StepN interface, mostly targeting the LFVM implementation.
All fuzzing tests are automatically run as unit-tests with the initial test data + any test data files found in
go/ct/testdata/fuzz/NameOfTheTest/*
. Such files are automatically generated but the fuzzing engine when a failure or panic is found.This PR does not:
such tasks are still up for discussion.