-
-
Notifications
You must be signed in to change notification settings - Fork 636
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
Ensure correct toolchain per clone. #6054
Ensure correct toolchain per clone. #6054
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Previously, if the Rust toolchain was changed, re-bootstrapping would proceed correctly in the first clone encountering the change but it would fail in other clones. Ensure the correct toolchain is set when building the symlink farm (but not needing to bootstrap the toolchain) to cover this case.
…tions of the toolchain are not or are corrupt.
3c6071d
to
8caa0f7
Compare
Went a bit further here and did it really right. Probably worth another look. |
function set_rust_toolchain() { | ||
( | ||
cd "${REPO_ROOT}" | ||
"${RUSTUP}" override set "${RUST_TOOLCHAIN}" >&2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be more explicit to use the rust-toolchain
file: https://github.com/rust-lang-nursery/rustup.rs#the-toolchain-file ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think so. Good idea.
This seals the current repo Rust toolchain version in a standard discoverable place. Also rename `bootstrap_rust.sh`'s exported function to reflect what it actually now does.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excellent!
This apparently needs to re-bootstrap the native engine binary and supporting changes to test infra were needed to ensure the new rust-toolchain file was available in the test buildroot as result.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like it'll be very cool. Thanks!
Previously, if the Rust toolchain was changed, re-bootstrapping would
proceed correctly in the first clone encountering the change but it
would fail in other clones. Ensure the correct toolchain is set when
building the symlink farm (but not needing to bootstrap the toolchain)
to cover this case.