-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
[BUG] Log message is not ideal on exhausting state space that is the image of View #1040
Comments
Ah, that's true. Would you prefer seeing: "No way to extend symbolic computation". |
I think that's just another phrasing of what is already given. I think the problem is that from the current message it's not very obvious that the deadlock is only occurring because previous solutions have been thrown out. It might make a user think their system model has a deadlock when in fact it doesn't. |
Actually, it's not. With
|
Oops. The fix was not good then |
@shonfeder, given the recent refactoring of the configuration options, what would be the optimal place for doing the following: if |
This is also an issue when passing a transition filter. |
Given that deadlock detection makes an additional call (and it's is incomplete anyways), it seems to be a good idea to me to set |
Really depends on the program logic. If it is an invariant of anything that takes checker options, then I think it should go in the converstion from configurations to "option groups": |
Description
When you generate multiple counterexamples with --max-error=k, and a View operator, if it is not possible to generate at least k counterexamples then the log contains this line 'Found a deadlock. No SMT model. E@14:57:23.621', which makes sense but is a bit confusing.
Input specification
The command line parameters used to run the tool
apalache-mc check --max-error=3 --view=View --inv=IsThree 2PossibleTraces.tla
Expected behavior
A nice log message like 'max counterexamples have been generated for the given view'
Log files
System information
apalache-mc version
]: APALACHE version 0.15.12 build 05d50b2The text was updated successfully, but these errors were encountered: