-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
Add tests for #26114 #32010
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
Add tests for #26114 #32010
Conversation
|
r? @brson (rust_highfive has picked a reviewer for you, use r? to override) |
cf00910 to
3f94fac
Compare
|
@bors try |
|
@bors try retry |
|
⌛ Trying commit b5be095 with merge 1e985d3... |
|
💥 Test timed out |
|
@bors: retry |
|
⌛ Trying commit b5be095 with merge a1cc5b6... |
|
💥 Test timed out |
|
@bors: retry |
|
⌛ Trying commit b5be095 with merge 605713f... |
|
💥 Test timed out |
|
@bors: retry clean |
|
⌛ Trying commit b5be095 with merge b0d224f... |
|
💥 Test timed out |
|
Not sure why this keeps timing out. Should I try submitting this again as a fresh pull request? |
|
I think these are all from the |
|
@alexcrichton I meant that I'm not sure why the |
|
I probably should have gotten to this earlier. Looks fine to me. |
|
@bors: r+ b5be095 |
|
I'm going to assume that it's the try bots being weird, since they don't get used much. |
|
It looks like this never re-entered the merge queue after @Aatch reviewed it. It still only has the failed try run on there. |
|
@bors r=Aatch try- retry |
|
💡 This pull request was already approved, no need to approve it again.
|
|
📌 Commit b5be095 has been approved by |
|
⌛ Testing commit b5be095 with merge 2af3dd7... |
|
Probably needed that retry there. back in the queue. |
|
@Manishearth thanks! |
First step in fixing #26114