-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
rustup can't update nightly #51699
Comments
Related to #51680? |
This is causing problems on Travis too, see for example rustfmt |
This affects the mozilla overlay for nixpkgs as well, since that uses the same URLs. |
Comparison of nightly and stable metadata for rustup:
Somehow |
Regression caused by #50336. diff --git a/src/bootstrap/dist.rs b/src/bootstrap/dist.rs
index 9092deeac461..73cda4b436d4 100644
--- a/src/bootstrap/dist.rs
+++ b/src/bootstrap/dist.rs
@@ -1756,6 +1740,7 @@ impl Step for HashSign {
cmd.arg(builder.package_vers(&builder.release_num("cargo")));
cmd.arg(builder.package_vers(&builder.release_num("rls")));
cmd.arg(builder.package_vers(&builder.release_num("rustfmt")));
+ cmd.arg(builder.llvm_tools_vers());
cmd.arg(addr);
builder.create_dir(&distdir(builder)); |
@kennytm you were few minutes faster. rust/src/tools/build-manifest/src/main.rs Lines 178 to 179 in 8d22af8
|
@mati865 You're looking at an old commit 😄 rust/src/tools/build-manifest/src/main.rs Lines 213 to 215 in 4b17d31
|
@kennytm Oops, commit from 27 Jul 2017. |
Recognize the extra "LLVM tools versions" argument to build-manifest. Fix rust-lang#51699.
Updating with a previous version such as |
Indeed, this breaks every single project having CI against Rust nightly. |
The nightlies of 2018-06-22 don't work (rust-lang/rust#51699).
(cherry picked from commit 09581dc)
rust-lang/rust#51699 has broken the nightly Rust toolchain. Our Travis configuration allows failures when building with that toolchain, but we use nightly rustfmt when building with all toolchains, so the bustage affects our stable and beta builds too. To work around the problem, this branch uses a specific rustfmt nightly rather than the latest one. (We might want to keep doing this even after the bustage is fixed, to avoid such bustage in the future.)
For anyone wondering, PR #51703 has fixed the bug. It will take until the next scheduled nightly upload until rustup starts working again. |
Should rustup tests be added as part of the release process? |
There is already an open issue about testing rustup. rust-lang/rust-central-station#17 |
@est31 when is the next scheduled nightly upload? |
@slaiyer It should be in progress right now. https://github.com/rust-lang/rust-central-station/blob/12b28bc1c2/crontab#L7 runs at midnight UTC. |
✗ rustup update nightly
info: syncing channel updates for 'nightly-x86_64-apple-darwin'
info: latest update on 2018-06-22, rust version 1.28.0-nightly (662c70a59 2018-06-21)
info: downloading component 'rustc'
error: failed to parse url: 1.28.0-nightly (662c70a59 2018-06-21)/2018-06-22/rustc-nightly-x86_64-apple-darwin.tar.xz
info: caused by: relative URL without a base |
Nightly should release within the next 30 minutes, probably the next 10-15 minutes. Until then, yes, the command won't work. |
2018-06-23 is live and the url is fixed |
The nightlies of 2018-06-22 don't work (rust-lang/rust#51699, https://twitter.com/RustStatus/status/1010240719527739392?s=19).
The nightlies of 2018-06-22 don't work (rust-lang/rust#51699, https://twitter.com/RustStatus/status/1010240719527739392?s=19).
Same issue with current meta for nightly:
From https://static.rust-lang.org/dist/channel-rust-nightly.toml: manifest-version = "2"
date = "2019-01-10"
[pkg.rustc.target.x86_64-unknown-linux-gnu]
available = true
url = "nightly/2019-01-10/rustc-nightly-x86_64-unknown-linux-gnu.tar.gz"
hash = "f4b5c77ce75ffdee97d460f03b8f84dd49129143c8e896e44d4512de2c0a686a"
xz_url = "nightly/2019-01-10/rustc-nightly-x86_64-unknown-linux-gnu.tar.xz"
xz_hash = "54a1b1791612651ded4c052c2c29a9b2e681344da4cebdc2382d14b62936f4fa" |
There seems to be a malformed URL in the rustup manifest since 1.27 got released today.
The text was updated successfully, but these errors were encountered: