Reduce verbosity for InvalidCompilation errors #2417
Merged
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.
Following #2011
Problem
When trying to analyze a bogus Solidity file,
slither
output is a bit crowded with multiple stacktraces of exception thrown (as shown in the previous issue).Tentative solution
If the compilation fails in Crytic with an
InvalidCompilation
exception, we don't print the backtrace and instead exit with a new error code (2
).The new output will be like this:
A new test is added (maybe the location is wrong though) to test this behavior: