-
Notifications
You must be signed in to change notification settings - Fork 13.3k
[BETA] Update cargo #62911
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[BETA] Update cargo #62911
Conversation
|
@bors: r+ |
📌 Commit a4358d466e514e72fc767c9ad0e3f1d1d771b2f0 has been approved by |
⌛ Testing commit a4358d466e514e72fc767c9ad0e3f1d1d771b2f0 with merge c4f6cb24ee32c5234a9a652529bcf2b233505c7a... |
💥 Test timed out |
@bors: retry Looks like LLVM fell out of cache |
@bors p=-1 |
a4358d4
to
501f828
Compare
@pietroalbini Are you planning a beta rollup? Just FYI, I just added a new commit here. @bors r=alexcrichton |
📌 Commit 501f828 has been approved by |
Yeah in the next few days, which is the reason for the p=-1. |
@bors r- This should still be considered approved, but I'll include it in the rollup tomorrow. |
@bors r=alexcrichton p=-1 |
📌 Commit 501f828 has been approved by |
[beta] Rollup backports Cherry picked: * Updated RELEASES.md for 1.37.0 #63147 * Require a value for configure --debuginfo-level #62906 * Make the parser TokenStream more resilient after mismatched delimiter recovery #62887 * ci: move .azure-pipelines to src/ci/azure-pipelines #63242 Rolled up: * [BETA] Update cargo #62911 * [beta] Backport #61207 #63254 r? @ghost
☔ The latest upstream changes (presumably #63262) made this pull request unmergeable. Please resolve the merge conflicts. |
3 commits in d0f828419d6ce6be21a90866964f58eb2c07cd56..9edd089168f8795b3890bc3daf5b99f03e9f8765
2019-07-23 21:58:59 +0000 to 2019-08-02 09:26:36 -0700
cargo new
in root directory. ([BETA] Fixcargo new
in root directory. cargo#7128)