Conversation
|
r? @aturon (rust_highfive has picked a reviewer for you, use r? to override) |
|
a2f85a7 to
ec35869
Compare
|
@bors: r+ p=1 |
|
📌 Commit ec358693fcd56df0b34e5d8b05541adfb1f59035 has been approved by |
ec35869 to
7613bbb
Compare
|
Er wrong PR r+'d! r? @nrc |
|
@bors r+ p=1 |
|
📌 Commit 7613bbb42c77544c98cee5d92d8364c41bf84c08 has been approved by |
|
⌛ Testing commit 7613bbb42c77544c98cee5d92d8364c41bf84c08 with merge 80095388e836bcf9375e8295f839797d0f32bb8c... |
|
💔 Test failed - status-appveyor |
|
@bors: retry |
|
🔒 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 |
Brings in some fixes and stabilizations!
7613bbb to
01127ca
Compare
|
@bors: r=nrc |
|
@bors: retry |
Update Cargo submodule Brings in some fixes and stabilizations!
|
⌛ Testing commit 01127ca with merge b6e9531b52b472d3ba8ab3dd313640101c5236ca... |
|
💔 Test failed - status-appveyor |
|
⌛ Testing commit 01127ca with merge f6d457dcfd7a80d6a7b0244a37c85f2222f96651... |
|
💔 Test failed - status-appveyor |
|
@bors p=11 |
Update Cargo submodule Brings in some fixes and stabilizations!
|
☀️ Test successful - status-appveyor, status-travis |
Brings in some fixes and stabilizations!