-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Update Clippy and cargo #63587
Update Clippy and cargo #63587
Conversation
|
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
Huh, we had to fix this in Clippy the other way around? rust-lang/rust-clippy#4378 🤔 |
I pointed the Clippy submodule to rust-lang/rust-clippy@ebd3eea, which will be on the master branch, once rust-lang/rust-clippy#4391 is merged. (Except the update of the |
Also specify patch version of toml crate cc rust-lang/rust#63587 The patch update of the toml crate to version 0.5.3 recently broke some tests: #4378. For rustc, we have to define the complete version though. changelog: none
Updated to rust-lang/rust-clippy#4395 |
@bors r+ p=1 |
📌 Commit 397f0c8b1a077c02aca5f2ad19eca52610a89ac6 has been approved by |
This will probably not merge because #63627 broke clippy again |
@bors r- Is this possible now? |
Nice. |
Rebased it on the auto merge of rust-lang/rust-clippy#4398. So this can be r+ed again once this is merged. |
@bors delegate+ |
✌️ @flip1995 can now approve this pull request |
Oh, nevermind @bors r+ |
📌 Commit bed48c7c3c8af4a9656cb514975a5cba5ddc7428 has been approved by |
☔ The latest upstream changes (presumably #63640) made this pull request unmergeable. Please resolve the merge conflicts. |
🔒 Merge conflict This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again. How do I rebase?Assuming
You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial. Please avoid the "Resolve conflicts" button on GitHub. It uses Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Error message
|
@bors r+ You can do it bors! :) |
📌 Commit 2bf27398836dec2cf8a71eb2d4251e8e8b4051c8 has been approved by |
🔒 Merge conflict This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again. How do I rebase?Assuming
You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial. Please avoid the "Resolve conflicts" button on GitHub. It uses Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Error message
|
☔ The latest upstream changes (presumably #63579) made this pull request unmergeable. Please resolve the merge conflicts. |
This will also need another update to rust-lang/rust-clippy@1055cf5 |
@bors r+ |
📌 Commit 96c3ec1 has been approved by |
Update Clippy and cargo r? @Manishearth @oli-obk
☀️ Test successful - checks-azure |
📣 Toolstate changed by #63587! Tested on commit 51879c3. 🎉 clippy-driver on windows: build-fail → test-pass (cc @Manishearth @llogiq @mcarton @oli-obk @phansch, @rust-lang/infra). |
Tested on commit rust-lang/rust@51879c3. Direct link to PR: <rust-lang/rust#63587> 🎉 clippy-driver on windows: build-fail → test-pass (cc @Manishearth @llogiq @mcarton @oli-obk @phansch, @rust-lang/infra). 🎉 clippy-driver on linux: build-fail → test-pass (cc @Manishearth @llogiq @mcarton @oli-obk @phansch, @rust-lang/infra).
r? @Manishearth @oli-obk