You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, save-cli can only fail a test if there're unmatched warnings (ExecutionResult.code is preserved but never read).
Yet, we currently cannot differentiate between:
the case when the number of warnings is zero (as expected), and
the case when the tool under test hasn't even run.
For instance, KtLint may return 0 on success and 1 on failure (if warnings were found), but the return code willl be 127 if Java is not installed (POSIX), and we can't reliably detect that yet.
Currently,
save-cli
can only fail a test if there're unmatched warnings (ExecutionResult.code
is preserved but never read).Yet, we currently cannot differentiate between:
For instance, KtLint may return 0 on success and 1 on failure (if warnings were found), but the return code willl be 127 if Java is not installed (POSIX), and we can't reliably detect that yet.
We need smth like
The above will, particularly, allow us to easily diagnose problems like:
<n>
.More details: Exit Codes With Special Meanings.
The text was updated successfully, but these errors were encountered: