Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Feel free to merge this PR after the Viper release.
This PR simply provides more error reporting in case the Boogie process does not work as expected.
These changes were motivated by Gobra due to the following scenario: I wanted to upgrade the JVM version we use within the Docker image that Gobra produces as part of its CI. While doing so, I noticed that all our Carbon-based testcases failed and the only error I got was "java.io.IOException: Broken pipe". After applying this PR's changes, I additionally got "Boogie stderr (early):\n No usable version of libssl was found" which was immensely useful to eventually resolve the issue within our Docker image