You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to install the beta channel in order to test Rust 2018, but I ran into rust-lang/rust#55817. It was difficult to figure out what was happening; I was quite confused by the rustup output:
$ rustup install beta
info: syncing channel updates for 'beta-x86_64-apple-darwin'
info: latest update on 2018-11-09, rust version 1.31.0-beta.5 (bf00632e3 2018-11-08)
beta-x86_64-apple-darwin unchanged - (toolchain not installed)
I thought I must be using the wrong rustup commands, and spent a lot of time trying different things before concluding that it was not user error.
My monthly Travis build failed without any changes on my part. I did pin
Rust versions, but I also test on "nightly", "beta", and "stable", which
are mutable. "Beta" today is not the same as "beta" one month ago, so
other people can still break my build. Rustup is provided by Travis so I
cannot pin Rustup either. Travis might have updated it to a broken
version, or the Rust project might have broken their hosting of the beta
channel for OS X upstream. I am not sure what the underlying issue is,
but from skimming the comments it looks like it will sort itself out. In
the mean time, disable testing on beta on OS X.
Related issues:
rust-lang/rustup#1539rust-lang/rust#55817
I believe that this won't happen on beta any more thanks to process changes; but I wonder if there's a way we can reproduce this now. Does anyone know if we have the beta manifests from the past?
There has been no movement on this, nor any reproduction of it. I'm going to close the issue. If something like this comes up in the future, we can open a fresh issue to discuss.
I wanted to install the beta channel in order to test Rust 2018, but I ran into rust-lang/rust#55817. It was difficult to figure out what was happening; I was quite confused by the rustup output:
I thought I must be using the wrong rustup commands, and spent a lot of time trying different things before concluding that it was not user error.
Could rustup have better error diagnostics for this case? It's come up a few times now: rust-lang/rust#55817, rust-lang/rust#46391, rust-lang/rust#46396.
The text was updated successfully, but these errors were encountered: