-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
rustbuild: save-analysis inadvertently nuked #38734
Labels
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
Comments
BTW the failure on the win32 beta bot (ouch!) is not related to this. It's most likely a Windows hiccup. |
sanxiyn
added
the
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
label
Dec 31, 2016
bors
added a commit
that referenced
this issue
Jan 1, 2017
rustbuild: save the save analysis Fixes #38734. ~~call me the nightly firefighter~~ r? @alexcrichton
Ahhhh big failure of mine. I'm focusing on the generation part (the envvar) and forgot to touch the |
bors
added a commit
that referenced
this issue
Jan 1, 2017
rustbuild: fix dist-analysis with full bootstrap disabled Really fixes #38734, per discussion in #38752 which was solving the underlying problem the wrong way. This just mirrors the [similar logic] in documentation building as suggested, that just takes the stage1 compiler artifacts instead in case of non-full-bootstrap builds. Actually copying the artifacts around seems to be unnecessary. r? @alexcrichton [similar logic]: https://github.com/rust-lang/rust/blob/7b659cfdbce094a790dbb246da2681a47565782a/src/bootstrap/doc.rs#L140-L144
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
So #38631 invalidated the assumption that the final stage is stage2, but this piece of code still thought so, so the save-analysis data is never generated. This enraged the bots.
Let's polish rustbuild with some more <3 so that we could have a fresh nightly for a nice New Year gift to everyone...
The text was updated successfully, but these errors were encountered: