cargo clean -p only cleans the build for a version with zero arguments

[nikomatsakis]

Given a clean checkout of foo:

cargo clean -p foo
cargo rustc -p foo -- -Zverbose

cargo clean -p foo
cargo rustc -p foo -- -Zverbose

Only the first cargo rustc will actually build. But if you change the argument to -Z verbose the second time, it will build (but only once). My hypothesis (which @alexcrichton confirmed) is that each generates a distinct fingerprint, and cargo clean -p foo is looking for a version with no arguments.

I would expect it rather to clean all builds related to foo with any arguments.

[ghost]

Hitting this when compiling for a different target:

$ cargo run -v --target i686-unknown-linux-gnu
$ cargo clean -vv -p usize
(nothing is cleaned)
$ cargo run -v --target i686-unknown-linux-gnu
...
Fresh usize v0.1.0 (file:///home/xftroxgpx/build/2nonpkgs/rust.stuff/rustlearnage/usize)
...
$ cargo clean -vv -p usize --target i686-unknown-linux-gnu
    Removing /home/xftroxgpx/build/2nonpkgs/rust.stuff/rustlearnage/target/i686-unknown-linux-gnu/debug/usize
    Removing /home/xftroxgpx/build/2nonpkgs/rust.stuff/rustlearnage/target/i686-unknown-linux-gnu/debug/.fingerprint/usize-d5bf39b5c2514907
    Removing /home/xftroxgpx/build/2nonpkgs/rust.stuff/rustlearnage/target/i686-unknown-linux-gnu/debug/deps/usize-d5bf39b5c2514907

Used #5059 to show Removed filespaths.

OP clearly explains the issue, thanks!

[stale]

As there hasn't been any activity here in over 6 months I've marked this as stale and if no further activity happens for 7 days I will close it.

I'm a bot so this may be in error! If this issue should remain open, could someone (the author, a team member, or any interested party) please comment to that effect?

The team would be especially grateful if such a comment included details such as:

• Is this still relevant?
• If so, what is blocking it?
• Is it known what could be done to help move this forward?

Thank you for contributing!

If you're reading this comment from the distant future, fear not if this was closed automatically. If you believe it's still an issue please leave a comment and a team member can reopen this issue. Opening a new issue is also acceptable!

[dwijnand]

Under-compiling is dangerous. Let's try and fix this issue.