nightly version off-by-one

[hellow554]

I don't know if this is a rustup or a rust problem, let's start this here.

op@VBOX ~> rustup default nightly-2019-02-02
info: using existing install for 'nightly-2019-02-02-x86_64-unknown-linux-gnu'
info: default toolchain set to 'nightly-2019-02-02-x86_64-unknown-linux-gnu'

  nightly-2019-02-02-x86_64-unknown-linux-gnu unchanged - rustc 1.34.0-nightly (852701ad6 2019-02-01)

op@VBOX ~> rustc --version
rustc 1.34.0-nightly (f6fac4225 2019-02-03)

Note the difference between 2019-02-03, 02 and 01 This is very confusing and I don't know which version I do now have.

[hellow554]

Note that this not apply to this nightly version only, but also for others, e.g.

op@VBOX ~> rustup default nightly-2019-01-15
info: using existing install for 'nightly-2019-01-15-x86_64-unknown-linux-gnu'
info: default toolchain set to 'nightly-2019-01-15-x86_64-unknown-linux-gnu'

  nightly-2019-01-15-x86_64-unknown-linux-gnu unchanged - rustc 1.33.0-nightly (03acbd71c 2019-01-14)

op@VBOX ~> rustc --version
rustc 1.33.0-nightly (03acbd71c 2019-01-14)

op@VBOX ~> rustup default nightly-2018-12-29
info: using existing install for 'nightly-2018-12-29-x86_64-unknown-linux-gnu'
info: default toolchain set to 'nightly-2018-12-29-x86_64-unknown-linux-gnu'

  nightly-2018-12-29-x86_64-unknown-linux-gnu unchanged - rustc 1.33.0-nightly (60e825389 2018-12-28)

op@VBOX ~> rustc --version
rustc 1.33.0-nightly (60e825389 2018-12-28)

[h-michael]

Could you show cat $HOME/.rustup/settings.toml ?

[hellow554]

default_toolchain = "nightly-2018-12-29-x86_64-unknown-linux-gnu"
telemetry = false
version = "12"

[overrides]

[h-michael]

Thanks, and could you show rustup show ?

[hellow554]

op@VBOX ~> rustup show
Default host: x86_64-unknown-linux-gnu

installed toolchains
--------------------

stable-x86_64-unknown-linux-gnu
beta-x86_64-unknown-linux-gnu
nightly-2018-03-01-x86_64-unknown-linux-gnu
nightly-2018-06-01-x86_64-unknown-linux-gnu
nightly-2018-09-01-x86_64-unknown-linux-gnu
nightly-2018-11-01-x86_64-unknown-linux-gnu
nightly-2018-12-01-x86_64-unknown-linux-gnu
nightly-2018-12-15-x86_64-unknown-linux-gnu
nightly-2018-12-20-x86_64-unknown-linux-gnu
nightly-2018-12-21-x86_64-unknown-linux-gnu
nightly-2018-12-22-x86_64-unknown-linux-gnu
nightly-2018-12-24-x86_64-unknown-linux-gnu
nightly-2018-12-26-x86_64-unknown-linux-gnu
nightly-2018-12-29-x86_64-unknown-linux-gnu (default)
nightly-2019-01-01-x86_64-unknown-linux-gnu
nightly-2019-01-03-x86_64-unknown-linux-gnu
nightly-2019-01-04-x86_64-unknown-linux-gnu
nightly-2019-01-05-x86_64-unknown-linux-gnu
nightly-2019-01-09-x86_64-unknown-linux-gnu
nightly-2019-01-11-x86_64-unknown-linux-gnu
nightly-2019-01-12-x86_64-unknown-linux-gnu
nightly-2019-01-13-x86_64-unknown-linux-gnu
nightly-2019-01-14-x86_64-unknown-linux-gnu
nightly-2019-01-15-x86_64-unknown-linux-gnu
nightly-2019-02-02-x86_64-unknown-linux-gnu
nightly-2019-02-03-x86_64-unknown-linux-gnu
nightly-x86_64-unknown-linux-gnu
ci-790f4c566d9802dfcadc26398dde2051cfe6ec9f-x86_64-unknown-linux-gnu
1.0.0-x86_64-unknown-linux-gnu
1.1.0-x86_64-unknown-linux-gnu
1.14.0-x86_64-unknown-linux-gnu
1.21.0-x86_64-unknown-linux-gnu
1.31.1-x86_64-unknown-linux-gnu

active toolchain
----------------

nightly-2018-12-29-x86_64-unknown-linux-gnu (default)
rustc 1.33.0-nightly (60e825389 2018-12-28)

(I hunted down an ICE lately, therefore I have a lot of nightlys installed ^^)

[h-michael]

op@VBOX ~> rustup default nightly-2019-02-02
info: using existing install for 'nightly-2019-02-02-x86_64-unknown-linux-gnu'
info: default toolchain set to 'nightly-2019-02-02-x86_64-unknown-linux-gnu'

nightly-2019-02-02-x86_64-unknown-linux-gnu unchanged - rustc 1.34.0-nightly (852701ad6 2019-02-01)

Rust nightly is uploaded everyday at UTC 00:00 +00:00.
Rust nightly build is success build version at that time.
So almost certainly, the date shown with commit hash is the previous day.

[kinnison]

This is indeed a side effect of the date stamps and when toolchains are built. This is a long-standing thing and there's not a lot rustup can do about it, sorry.

If there's no suggestion for a way for rustup to help you, then I request you close the issue.

[hellow554]

Thanks, for your answers :) I see, that there is nothing one could do right now.

[RalfJung]

This was a duplicate of rust-lang/rust#51533.