On 18/10/2017 23:26, Simon Sapin wrote:
Anyway, some of the affected commits have a rust-toolchain or
rust-nightly-date file that contains a date. You can then run something
like `rustup override set nightly-2017-10-13` to get that version and
tell rustup to use it when under the current directory.
Other commits however have a rust-commit-hash file, and there’s not
necessarily a Nightly with that exact commit. Go to e.g.
https://github.com/rust-lang/rust/commit/23de823e93dc19ef1b9cb65b48860a892cd6ff18
(or run `git show 23de823e93dc19ef1b9cb65b48860a892cd6ff18` in a local
clone of the rust repo), look at the merge commit’s date, and try the
next day’s nightly. (Nighties in rustup are indexed by date of
publication, but are picked from the last merge before midnight, so on
the previous day.)
Commits after https://github.com/servo/servo/pull/18942 should bootstrap
successfully "forever"[1] if "llvm-assertions = true" is configured in
the [build] section of .servobuild. (The default is false, which uses
"alternate" rustc builds which are not yet available officially.)
[1] As long as corresponding Nightly builds are available on
static.rust-lang.org, which is the location that the Rust infra team
considers "stable and public".
--
Simon Sapin
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
