Skip to content
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

Allow some solvers to fail when using prover=any #447

Closed
atomb opened this issue Sep 25, 2017 · 5 comments
Closed

Allow some solvers to fail when using prover=any #447

atomb opened this issue Sep 25, 2017 · 5 comments
Labels
UX Issues related to the user experience (e.g., improved error messages)

Comments

@atomb
Copy link
Contributor

atomb commented Sep 25, 2017

Right now, if any of the provers invoked using prover=any fails, Cryptol quits. It would be more convenient to just ignore (and maybe mention) any prover crashes, and simply report the result of the first successful prover. See also #436.

@jpziegler
Copy link
Contributor

Now that we have a bunch of new types in Cryptol, this also crops up when a solver doesn't support a particular theory:

┏━╸┏━┓╻ ╻┏━┓╺┳╸┏━┓╻  
┃  ┣┳┛┗┳┛┣━┛ ┃ ┃ ┃┃  
┗━╸╹┗╸ ╹ ╹   ╹ ┗━┛┗━╸
version 2.7.1 (2ce982a, modified)

Loading module Cryptol
Cryptol> :s prover=any
Cryptol> :sat \(x,y) -> x*y == (2147483647:Integer) /\ x > 1 /\ y > 1

SBV error:
SBV: Given problem needs unbounded integers
*** Which is not supported by SBV for the chosen solver: Boolector

Note that most of the solvers don't support this theory; it just happens to choose Boolector to complain about. (I was running with all 6 solvers available.)

@atomb
Copy link
Contributor Author

atomb commented Oct 25, 2019

Let's see if we can make this work better with What4.

@brianhuffman
Copy link
Contributor

If this is a problem with SBV, then we should open a ticket on the SBV repository.

@robdockins robdockins added the UX Issues related to the user experience (e.g., improved error messages) label Jun 5, 2020
@robdockins
Copy link
Contributor

Did we open an SBV ticket for this?

@robdockins
Copy link
Contributor

Fixed via #788.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
UX Issues related to the user experience (e.g., improved error messages)
Projects
None yet
Development

No branches or pull requests

4 participants