Increase SMT timeout in integration tests #2440
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
geo2a
force-pushed
the
georgy/increas-smt-timeout
branch
from
7b83766 to
1f6aeb5
Compare
|
This is not needed anymore, as we do now have a more robust SMT sovler interface in Booster. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A PR to the Haskell backend will strengthen Booster's simplifications, potentially making the predicates we send to the SMT solver from Booster more complicated. Some of the recently re-enabled tests fail with
kore-rpc-boosterdue to Booster's SMT solver interface timing out. Until we have implemented a retry mechanism in Booster, I propose to increase the solver time-out.