Re-enable linkcheck after moving std#74861
Conversation
|
@mark-i-m Are you planning on fixing the tests here? I'm working on local builds of this currently to try and push patches |
|
Pushed a commit which passes linkcheck for me locally. |
|
@bors r+ p=1 This re-enables testing so we should land it as quickly as possible. |
|
📌 Commit c71ef626972adee385c96e567c8f4a7863450464 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 #73964) made this pull request unmergeable. Please resolve the merge conflicts. |
c71ef62 to
6726ca2
Compare
|
Rebased. Should be ready for r+ |
|
@bors r+ p=1 |
|
📌 Commit 6726ca2 has been approved by |
|
⌛ Testing commit 6726ca2 with merge 1d765131c1ae2cae6e9bc1e92372dd37133048cd... |
|
💔 Test failed - checks-azure |
|
@bors retry hopefully spurious?! |
|
☀️ Test successful - checks-actions, checks-azure |
No description provided.