Conversation
|
(rust_highfive has picked a reviewer for you, use r? to override) |
|
|
@bors: r+ p=1 |
|
📌 Commit 11cd27ad669b16d2e1c79becda60934a602b6b76 has been approved by |
|
⌛ Testing commit 11cd27ad669b16d2e1c79becda60934a602b6b76 with merge ff5921fa666987ba79c943aa434ac742d6ab61db... |
|
💔 Test failed - checks-azure |
|
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 |
Hmm, is this a temporal error or a persistent one due to Azure Pipelines? Asking because the error did not show up in the CI of rustfmt which runs on Travis and AppVeyor. If it's the latter then I will skip the test for now. |
|
Updated rustfmt to ignore tests that require running a built rustfmt binary in 72244ab. |
|
@bors: r+ |
|
📌 Commit 72244ab6f8eba3eeb63792ff659221b09fee41d6 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 |
72244ab to
d8ffe7d
Compare
|
Resolved conflicts on Cargo.lock. |
|
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 |
|
The test failure seems unrelated to the rustfmt update to me. |
|
@bors: r+ |
|
📌 Commit d8ffe7d has been approved by |
Update rustfmt to 1.3.3 This PR updates rustfmt to 1.3.3 which fixes the bug in #62432 (comment).
|
☀️ Test successful - checks-azure |
This PR updates rustfmt to 1.3.3 which fixes the bug in #62432 (comment).