-
Notifications
You must be signed in to change notification settings - Fork 771
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
vm: adjust test runner with verkle state management #3716
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. |
What is the status of this? |
I'm still using it to try and run the verkle test fixtures but it's not ready for merging. We still have some blockers when running verkle at genesis that I don't have a solution for. Notably, if verkle is at genesis, we have to figure out how to hack in an execution witness or else relax the requirements for creating verkle blocks. I have ideas but none are really elegant or don't introduce tech debt we don't want |
…s witness and proper handling for 4762 and 2935
* Add simple cache to access witness * flush cache at end of tx * Flush system AW cache * add tests * fix verkle cache flushing bug * address feedback
…ereumjs-monorepo into vm/verkle-testing
This PR improves the test runner so that a
stateManager
option can be passed in order to use a non-default (default being MerkleStateManager) state manager (for now, the only other option isstateManager=verkle
, which will instantiate a StatefulVerkleStateManager to run the requested tests.