-
Notifications
You must be signed in to change notification settings - Fork 261
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
Improve Z3 detection #3233
Merged
Merged
Improve Z3 detection #3233
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
e8a4d17
Improve Z3 detection
atomb 47c1878
Merge remote-tracking branch 'upstream/master' into z3-path-version
atomb 94de5e6
Merge remote-tracking branch 'upstream/master' into z3-path-version
atomb b58c19d
Small cleanups
atomb 56e2038
Include z3 in more test packages
atomb 4f47175
Error later when failing to find Z3
atomb aff298e
Really only try to detect Z3 when it's being used
atomb 886c414
Improve behavior with bad prover path
atomb ba21bc8
Fix expected test output
atomb a9b8343
Merge remote-tracking branch 'upstream/master' into z3-path-version
atomb ce36954
Improve message when Z3 not found
atomb dbc9e84
Remove undocumented/invalid Unix platform comparison
atomb 45e6b7b
Compare Z3 version more idiomatically
atomb ca458ea
Merge remote-tracking branch 'upstream/master' into z3-path-version
atomb File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
// RUN: %exits-with 4 %baredafny verify %args --solver-path=doesNotExist "%s" > "%t" | ||
// RUN: %OutputCheck --file-to-check "%t" "%s" | ||
// CHECK: Fatal Error: ProverException: Cannot find specified prover:.* | ||
method m() { | ||
assert 1 + 1 == 2; | ||
} |
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
*** ProverException: Requested prover not found: 'Output/binz/z3' | ||
Fatal Error: ProverException: Cannot find specified prover: Output/binz/z3 |
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.
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.
How much are they hurting? Can you please describe the problem in a separate issue?
Also consider describing a range of versions in the conditional, rather than an exact version. Perhaps refactor this:
https://github.com/dafny-lang/dafny/pull/3233/files#diff-b3d55f76ae78d57880964c42ed16a37e9e6a8a3a7ca4022cb96367bccda8d667R80
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.
My experience is that any version newer than 4.8.5 works better with those options removed. I considered adding code to produce an error if it detects a version older than 4.8.5. If I do that, then the conditional above really should just be for a single version. What do you think?
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.
If you add this error if we detect a version older than 4.8.5, then yes that's fine. Where would you add this error?
If you do not add it in this PR, then I would prefer to see a version "<=" instead of just "=".
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.
I went for changing it to
<=
for now, since it's a little awkward to a signal an error from that location and I haven't actually seen evidence that versions < 4.8.5 don't work. Before we release 4.0 we may want to test those early versions and have a more complete strategy for how to handle the entire range of available versions.