-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
bump bootstrap compiler to 1.93 beta #149831
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
base: main
Are you sure you want to change the base?
Conversation
|
Some changes occurred in src/tools/clippy cc @rust-lang/clippy The Miri subtree was changed cc @rust-lang/miri |
|
r? mark-simulacrum |
0726fb6 to
d607440
Compare
This comment has been minimized.
This comment has been minimized.
Co-authored-by: León Orell Valerian Liehr <[email protected]>
|
@bors r+ |
|
@bors rollup=never |
|
@bors p=5 (just to get the bootstrap compiler bump done) |
bump bootstrap compiler to 1.93 beta r? release
|
@bors retry (timeout) |
|
A job failed! Check out the build log: (web) (plain enhanced) (plain) Click to see the possible cause of the failure (guessed by this bot) |
bump bootstrap compiler to 1.93 beta r? release
|
💥 Test timed out |
|
A job failed! Check out the build log: (web) (plain enhanced) (plain) Click to see the possible cause of the failure (guessed by this bot) |
|
@bors retry |
bump bootstrap compiler to 1.93 beta r? release
|
Seems like there is a hang when trying to run:
|
|
Seems like it's stuck on the same thing again, probably better to just kill it? |
|
crazy, spurriosu failuires are never non spurrious |
|
@bors r- |
|
can you even cancel a bors merge lol @bors retry |
|
|
Since you're talking about it, I've been wondering for quite some time what it's supposed to mean. From what I understand, "bors retry" retries a job with the existing r+, while "bors r-" withdraws any existing permission. What do I get wrong here? |
|
Yes, but |
r? release