-
Notifications
You must be signed in to change notification settings - Fork 0
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
Abort when Kore's simplifier throws DecidePredicateUnknown
#392
Conversation
ErrorDecidePredicateUnknown
ErrorDecidePredicateUnknown
ErrorDecidePredicateUnknown
ErrorDecidePredicateUnknown
ErrorDecidePredicateUnknown
DecidePredicateUnknown
KEVM Performace I would not expect a regression, but seems like there is one in some cases? Also improvement in some other cases. I was running with one worker, but some other stuff has been going on that machine...
|
Same sort of noisy result for Kontrol:
|
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. Left a small code change suggestion
Co-authored-by: Samuel Balco <[email protected]>
Fixes #373
This PR makes
kore-rpc-booster
return"execute"
responses with"reason": "aborted"
in cases when Kore's simplifier fails due toDecidePredicateUnknown
in the post-exec simplification inProxy.hs
.Scenario before
returning
JsonRpcError
resulted in loosing information gained by executing in booster for X steps + in kore for up to 1 step.Scenario now
this this change, we return the reached state (may be branching) and do not lose information anymore. Additionaly, we return the unknown predicate, so that
pyk
can decide what to do with these.PR to
pyk
that takes advantage of this feature by intrroducingUndecided
nodes to KCFG: runtimeverification/pyk#744