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
As far as I understand, the files in tests won't be checked by the current command because cargo rustc --lib will only build the files needed by the library. If there are any #[test] functions in these files, they will be checked, but the files in tests are obviously not part of the library, so they won't be checked.
And it seems that neither flycheck-rust nor flycheck has code to handle a test crate, so might as well report it here :)
There's a simple fix, and then there's the right fix, which is to eat what read-manifest feeds us completly, and is related to #8. I lean towards the latter, so I'll see what I can do about that.
The integration tests in my Cargo project (
tests/integration_test.rs
) are not being checked on save.flycheck-compile
gives me:cargo rustc --lib -- -Z no-trans -Z unstable-options --error-format\=json --test -L/home/me/libname/target/debug -L/home/me/libname/target/debug/deps
This command exits successfully even when there are errors in the integration tests. I don't know if this is an issue with
flycheck-rust
orflycheck
.The text was updated successfully, but these errors were encountered: