-
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
Can't install nightly-2019-01-10 #57488
Comments
pietroalbini
added
P-high
High priority
T-infra
Relevant to the infrastructure team, which will review and decide on the PR/issue.
C-bug
Category: This is a bug.
labels
Jan 10, 2019
This was referenced Jan 10, 2019
You can mitigate this by using |
Thanks for pinning this, just wanted to file a new issue. :) |
failed to parse url again 😅😂! |
ruuda
added a commit
to ruuda/claxon
that referenced
this issue
Jan 10, 2019
Temporarily disable builds that use the nightly toolchain, as it cannot be installed at the moment due to [1]. This issue will sort itself out soon, after which this commit can be reverted. It's a bit of a coincidence that the Travis cron build happened to run today, of all days; had it run tomorrow, then I probably would not have noticed a thing. [1]: rust-lang/rust#57488
bors
added a commit
that referenced
this issue
Jan 10, 2019
Integrate miri into build-manifest This fixes a mistake where miri was accidentally left out of the build-manifest parsing, meaning that today's nightly generated a manifest with invalid urls! Fixes #57488.
The issue will be fixed in the next nightly. Sorry for the trouble. |
No, I think it's fixed (despite finishing 20 minutes after UTC midnight 😅) |
Oh, ok then 🎉🎉🎉 |
alecmocatta
added a commit
to alecmocatta/palaver
that referenced
this issue
Jan 11, 2019
This reverts commit 74ddc43.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Installing rust nightly with rustup returns this error:
We're aware of this and a fix is pending in #57484. Sorry for the trouble!
The text was updated successfully, but these errors were encountered: