Non-zero status codes should better differentiate why (at which stage) the command failed #4379
Labels
A-diagnostics
Area: Error and warning messages generated by Cargo itself.
C-enhancement
Category: enhancement
P-low
Priority: Low
S-needs-design
Status: Needs someone to work further on the design for the feature or fix. NOT YET accepted.
At the moment, cargo only seem to support three values for status code (gathered from https://github.com/rust-lang/cargo/tree/master/tests):
cargo verify-project
is run with incorrect--manifest-path
TL;DR:
I would like for
cargo
to return different non-zero status codes for at least:Optionally:
Reasoning:
My problem is that I need a fix for this issue: kennytm/cargo-kcov#16, where
cargo kcov
should generate coverage report regardless of whether the tests failed or not. This issue would be much simpler to fix ifcargo
returned different status code for failures during compilation stage (in which casecargo kcov
needs to fail as well) and different status code if the tests failed (in which case it might continue with preparing coverage report).I can prepare PR for cargo myself, but I would like to know if this would be acceptable change for
cargo
beforehand.Regards
The text was updated successfully, but these errors were encountered: