-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
feat(vm): Allow running new VM in state keeper #2616
Conversation
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.
It is possible to not run the VM playground in integration tests now and instead run the state keeper with the shadow VM mode. I think the VM playground has its benefits; it could to complete integration tests and then fail if the playground has crashed (but this would optimally require to run it in a separate process which I haven't implemented). Would this approach make sense, or is it overly complicated?
Also, the Protobuf compatibility failure is intentional (caused by redefining experimental VM config in place of the VM playground config). It should disappear when comparing the feature branch and main
.
No performance difference detected (anymore) |
What ❔
Why ❔
Allows to monitor new VM performance regressions.
Checklist
zk fmt
andzk lint
.