-
Notifications
You must be signed in to change notification settings - Fork 781
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
evm: Precompile Tests #3189
evm: Precompile Tests #3189
Conversation
Codecov Report
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. |
Some general feedback here: yeah, I do think that it is really good if we have at least 1-2 simple test cases for each precompile in addition to the cross-client testing, also agree with @acolytec3 though that these particular precompiles have not such a high relevance (though they should nevertheless still not break consensus for sure), so we shouldn't take this too far. Changing error messages in the EVM is always a breaking change and I think it would not really be worth it here to adopt. So as a practical measure I would suggest that we delete the error message testing from the test cases and just concentrate on value testing here and simply see and take this as a small useful addition to the test setup (without discovering anything new). |
I agree changing the error messages is not worth it. I would change the tests to check that there is an error and fail if it does not error out. For reference, in |
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.
LGTM
This change increases coverage of evm precompiles by adding tests for the ripemd160 and blake2f precompile contracts as well as updating the ecrecover precompile tests.