-
Notifications
You must be signed in to change notification settings - Fork 149
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 infrastructure to KEVM for Maude Backend #2118
Conversation
8ffe98e
to
5a86ffd
Compare
6e82aaa
to
923fdbe
Compare
Okay, this is a problem. The test suite is so flaky that I've been spending days trying to get this merged. Days. |
I agree. Maybe the frontend could be made to not launch so many Z3s? That was an initial guess at a solution. Other things are being implemented, like better retrying in haskell backend on Z3 failures. We've also been reconfiguring parallelism and runner memory allocation. Investigation welcome! |
I mean, if we can't solve this immediately, what we really need to do is to implement a policy that only the oldest approved PR in the repo is allowed to be merged. Otherwise we end up with some PRs getting starved and never getting merged, ever. |
This PR modifies the kevm_pyk package so it is capable of building and using the maude backend when sending RPC requests. This code is still unused; the kontrol codebase needs a separate PR in order to start the maude backend and make use of it when invoking kontrol.