-
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
Panic when adding cyclic dev-dependency #3902
Comments
As a sidenote, I tried adding the library as its own dev-dependency to see whether that could be a way to pass feature flags to integration tests. I wasn't trying to break Cargo :) |
Wow I don't think I've ever seen an assertion get tripped in that module! |
alexcrichton
added a commit
to alexcrichton/cargo
that referenced
this issue
Apr 26, 2017
Don't actually need to assert that these are unique, it works both ways and we can have flavorful dependency graphs which otherwise trigger the assertions. Closes rust-lang#3902
bors
added a commit
that referenced
this issue
Apr 26, 2017
Relax overly strict asserts in dependency queue Don't actually need to assert that these are unique, it works both ways and we can have flavorful dependency graphs which otherwise trigger the assertions. Closes #3902
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When adding a library as its own dependency, Cargo detects it:
But when creating an integration test and adding the current library as dev-dependency, it panics on
cargo test
. Steps to reproduce:Backtrace:
(Fun fact: When running this with
RUST_BACKTRACE=1
, the backtrace takes reeeeally long to generate.)The text was updated successfully, but these errors were encountered: