-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cargo test --all-targets
does not work exactly as advertised
#5178
Comments
Looks like the default case (no |
Stricter need_dev_deps behaviour The previous PR (#5012) contained an unnecessary work-around for behaviour of `--all-targets` that was misunderstood. This PR removes that work-around and adds some tests and comments to clarify the behaviour for future contributors, which may help to make easier a future fix for #5177 and #5178.
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:
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! |
Yea, |
--all-targets fixes - Fix: `cargo test --all-targets` was running lib tests three times. - `--all-targets` help strings were wrong or misleading. - Minor cleanup to add `Proposal` type to maybe make the code more readable. Closes #5178.
Stop testing with `--all-targets` to ensure doctests run (seems like rust-lang/cargo#5178 might still exist).
Dummy crate, from
test::test_then_build
:Running
cargo test --all-targets
seems to test even less thancargo test
.Affects at least cargo
0.24.0
all the way up to current HEAD.Uncovered by proposed additions to #5146.
The text was updated successfully, but these errors were encountered: