-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Prepare the 1.22.0 beta #45160
Prepare the 1.22.0 beta #45160
Conversation
r? @aturon (rust_highfive has picked a reviewer for you, use r? to override) |
@bors: r+ p=100 This is the new beta! |
📌 Commit f119eda has been approved by |
⌛ Testing commit f119eda with merge 57a31e86ab294ff41333789b8cce10f80e83c256... |
💔 Test failed - status-appveyor |
|
⌛ Testing commit f119eda with merge 412796f33c0a2d4cae137d4c80bd41dc092dd73d... |
💔 Test failed - status-travis |
RLS failures?
|
@bors: retry I'm going to pray that's spurious... I can't reproduce locally unfortunately |
Prepare the 1.22.0 beta This updates the Cargo submodule a bit but is otherwise pretty routine.
💔 Test failed - status-travis |
RLS error again. Legit. |
@Xanewok would you be able to help out here perhaps? I'm not so good at debugging the RLS :( |
f119eda
to
c0b1133
Compare
@bors: r+ managed to track it down |
📌 Commit c0b1133 has been approved by |
This updates the Cargo submodule a bit but is otherwise pretty routine.
c0b1133
to
7ac017d
Compare
@bors: r+ |
📌 Commit 7ac017d has been approved by |
⌛ Testing commit 7ac017d with merge 9d050fb930d9032d75760704cbe8b4ae5973aba1... |
💔 Test failed - status-travis |
I think you need to include #45193. |
@alexcrichton hey, sorry, read the notification just now. What was the cause? Still need help debugging? |
@Xanewok ah it turned out that the RLS was rewriting Cargo.lock as it was using a newer version of Cargo, but the Cargo.lock was mounted on a readonly filesystem so that failed. That error then cascaded quite a bit into a bunch of failing test cases. |
Apparently the https urls are broken due to some certificate validation whatnots, and so far the least intrusive solution I've found is to just disable that.
@bors: r+ |
📌 Commit 07117cf has been approved by |
Prepare the 1.22.0 beta This updates the Cargo submodule a bit but is otherwise pretty routine.
☀️ Test successful - status-appveyor, status-travis |
This updates the Cargo submodule a bit but is otherwise pretty routine.