-
Notifications
You must be signed in to change notification settings - Fork 35
dependencies: heuristic to distinguish host and target artifacts #329
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
Conversation
Should this go into the changelog? |
02c5489 to
37d7e93
Compare
|
Yea, seems like a good addition for ppl to know that they can do more now |
I'd like to see a release but presumably that's a separate PR? |
|
Nah just do it in this one. I'll clarify that in the PR description |
35ec58d to
ab0d618
Compare
|
You new ci checks for lockfiles seem to be working |
|
Oddly, a bunch of lockfiles did update when I just changed the version, but the main one did not.^^ |
|
Nothing ensures that the tests have updated lockfiles though... ah well, another time. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This lockfile and ui_test_dep_bug also have some more changes from the "spanned" thing; doesn't seem worth a separate PR.
Fixes #327 by looking at the path in which artifacts are stored: if we pass
--targetto cargo, that will be different for host and target crates. If a non-proc-macro host crate shows up, we just ignore it during artifact gathering.I have confirmed that in the context of rust-lang/rust-clippy#14883 this makes the dependency build work.
TODO (check if already done)