Skip to content
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

Nightly toolchain version different than rustc version #53557

Closed
elichai opened this issue Aug 21, 2018 · 3 comments
Closed

Nightly toolchain version different than rustc version #53557

elichai opened this issue Aug 21, 2018 · 3 comments
Labels
T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.

Comments

@elichai
Copy link
Contributor

elichai commented Aug 21, 2018

Hi,
So I noticed it in nightly 2018-04-12 but I'm sure this apply to other nightlys.
I install toolchain rustup override set nightly-2018-04-12-x86_64-unknown-linux-gnu
But the rustc version is different rustc 1.27.0-nightly (ad610bed8 2018-04-11).

On the IRC people told me the reason is because the CI starts deployment at 11:00PM and it doesn't end until after the next day starts, this seems solvable pretty easy.

Don't you think it's better to have a consistent release date?

@eddyb
Copy link
Member

eddyb commented Aug 21, 2018

Note that the date in (ad610bed8 2018-04-11) is not a version, it's the timestamp of the last commit (from the last merged PR) before the nightly, i.e. ad610be. If no PRs get merged, it doesn't change.

cc @SimonSapin @alexcrichton This has been discussed before.

@SimonSapin
Copy link
Contributor

The previous attempt at fixing this broke some infra things and was reverted: rust-lang/rust-central-station#27

@estebank estebank added the T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. label Jan 19, 2019
@Mark-Simulacrum
Copy link
Member

Closing as duplicate of #51533.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

5 participants