-
Notifications
You must be signed in to change notification settings - Fork 90
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
Forbid unprefixed SHAs for toolchains #723
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.
Thanks!
@bors r+ This seems reasonable to me. |
Forbid unprefixed SHAs for toolchains This PR forbids unprefixed SHAs for toolchain arguments, to avoid crater hanging when they appear. I'm not sure this is fully valid though: I don't know if SHAs could appear in a `Toolchain`'s name (and `RustwideToolchain::dist()`) without being an error 😓. This commonly happens with `rustup-toolchain-install-master` but I don't know if a similar situation could arise within common crater usage. CI will surely fail: some of the used dependencies are broken on nightly right now, and clippy emits warnings -- both issues are fixed in #722. <sub>(this is [for](rust-lang/rust#122230 (comment)) `@oli-obk` and [for](rust-lang/rust#122502 (comment)) `@compiler-errors)</sub>`
💔 Test failed - checks-actions |
@bors r+ |
💡 This pull request was already approved, no need to approve it again.
|
☀️ Test successful - checks-actions |
1 similar comment
☀️ Test successful - checks-actions |
👀 Test was successful, but fast-forwarding failed: 422 Changes must be made through a pull request. |
This PR forbids unprefixed SHAs for toolchain arguments, to avoid crater hanging when they appear.
I'm not sure this is fully valid though: I don't know if SHAs could appear in a
Toolchain
's name (andRustwideToolchain::dist()
) without being an error 😓. This commonly happens withrustup-toolchain-install-master
but I don't know if a similar situation could arise within common crater usage.CI will surely fail: some of the used dependencies are broken on nightly right now, and clippy emits warnings -- both issues are fixed in #722.
(this is for @oli-obk and for @compiler-errors)