ehuss
commented
3 years ago Hm, that's a strange one! If you're able to still reproduce the problem, some things you could try:
- Run
cargo build --all-targets --verboseto make sure it is actually compiling the test (after saving the test file so it triggers a rebuild). - Run
cargo checkwith theCARGO_INCREMENTALenvironment variable set to0. This will determine if it is maybe an incremental cache problem. - Clean the
targetdirectory and try both commands again.
LER0ever
Problem
Running
cargo build --all-targetsdoes NOT show any errors (not even a single warning), and all targets run fine. But runningcargo check --all-targetsgives out errors that should not exists, and exits prematurely witherror: could not compile xxx. A detailed example is attached below.Steps
I haven't got the time to make a minimal reproducible case, but have a real project showcasing the error below.
Possible Solution(s)
Beyond my reach. But I would guess it's related to import resolution, in my case interpreting
Resulttostd::result::Resultinstead of the importedanyhow::Result.Notes
Output of
cargo version:Screenshot of the issue
In the screenshot, the left pane of the integrated terminal is running
cargo check --all-targets, and the right is runningcargo build --all-targets. The build works fine butcargo checkgives out 22 errors which I'm sure are not valid errors after examination.Most errors say "the trait
std::error::Erroris not implemented foranyhow::Error", which seems to me thatcargo checkthinks theResultisstd::result::Result, however all theResultin this project isanyhow::Result, so the error does not make sense.All the errors are reported by
cargo checkon test targetstests/*.rs. Runningcargo build --testsgives no error. Running the tests shows 100% pass. So it's likely a problem ofcargo check.