-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Package non-rust objects #65337
Package non-rust objects #65337
Conversation
Not sure how to properly test this. |
The best way to test this I think is to open another PR with the same commits as this one but targeting a This is going to take time though, so I'd like (as proposed in #65335 (comment)) to rollback #64823 in the meantime. |
The changes here look reasonable, even if it is presumably a bit unknown as to whether they actually fully fix things or not. I'm going to @bors r+ p=1 this PR with the goal of landing it nightly tonight. I believe we have enough time left that we can do the following:
This seems like a fast and reasonable approach to getting a working nightly tonight no matter what. |
📌 Commit d3cae76a7ece0b65b882c3e16f3dbd682c666fc5 has been approved by |
@bors p=50 |
⌛ Testing commit d3cae76a7ece0b65b882c3e16f3dbd682c666fc5 with merge 64b6a78b008d714e9e1a4ee15e17361dfa896887... |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
💔 Test failed - checks-azure |
I've seen this error in my internal CI when the source file inside |
d3cae76
to
bcc11ac
Compare
@@ -1144,6 +1144,7 @@ impl Build { | |||
pub fn copy(&self, src: &Path, dst: &Path) { | |||
if self.config.dry_run { return; } | |||
self.verbose_than(1, &format!("Copy {:?} to {:?}", src, dst)); | |||
if src == dst { return; } |
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.
Not sure why this is now necessary, but hey, it appears to work!
@bors try |
⌛ Trying commit 8d4210a with merge 64d69a848361a21d478014cce5b51a11e10aec51... |
☀️ Try build successful - checks-azure |
+1. Ideally we would run these tests with the post build artifacts in a clean environment to be able to diagnose PRs that change how things are packaged. Any chance of merging this soon ? |
Ah sorry, I missed that. Thanks for the info. |
Closing in favor of #65474 which includes this. |
Split the rustc target libraries into separate rustc-dev component This is re-applies a squashed version of #64823 as well as including #65337 to fix bugs noted after merging the first PR. The second PR is confirmed as fixing windows-gnu, and presumably also fixes other platforms, such as musl (i.e. #65335 should be fixed); `RUSTUP_DIST_SERVER=https://dev-static.rust-lang.org rustup toolchain install nightly-2019-10-16` can be installed to confirm that this is indeed the case.
Split the rustc target libraries into separate rustc-dev component This is re-applies a squashed version of #64823 as well as including #65337 to fix bugs noted after merging the first PR. The second PR is confirmed as fixing windows-gnu, and presumably also fixes other platforms, such as musl (i.e. #65335 should be fixed); `RUSTUP_DIST_SERVER=https://dev-static.rust-lang.org rustup toolchain install nightly-2019-10-16` can be installed to confirm that this is indeed the case.
Fixes #65335
I'd like to use this opportunity to talk about increasing test coverage of tier 2 targets to at least make sure a "hello world" binary can be succesfully linked. There have been similar issues for individual targets in the past, but now we have one affecting several tier 2 targets (and even a tier 1 target).
r? @Mark-Simulacrum
cc @cuviper