Time limits for SystemTests #80
Merged
Conversation
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
|
Looks good, it would be nice to also have a timeout on the subprocess terminating, and the unit tests themselves eventually, but this solves the problem. |
|
Yeah, it could be good to have those in the future but I'm not really worried about them for now and they're more of a hassle. Failure to terminate is just an issue with Z3 called by Boogie and this handles that. |
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.
Addressing #77 a little bit. With these time limits the tests still take far too long on the latest Boogie (~15 minutes on Boogie 3.0.4 vs. ~4 minutes on 2.16.0 on my machine) but at least they're runnable.