runtimeverification / runtimeverification/haskell-backend
Make SMT timeout increase strategy configurable
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 224
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
In a recent PR, we have changed the SMT retries logic in Kore to scale the timeout exponentially.
When combined with the work to empower the simplifications Booster by using the SMT solver there as well, this leads to very long queries that still result in Unknown in Kore.
In order to have finer control, we need to introduce a command-line option that would allow to configure the scaling strategy:
--smt-timeout-scaling linearwill use the factors2, 3, 4, ...--smt-timeout-scaling expwill use the factors2, 4, 8, ...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the SMT retry changes in PR 3860 and the Booster-related work in PR 3904, then locate Kore's SMT retry logic and command-line option definitions. Add the --smt-timeout-scaling setting with linear factors 2, 3, 4 and exp factors 2, 4, 8, and verify both strategies are applied to retries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- backend, cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100