-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
[beta] Update cargo #74593
[beta] Update cargo #74593
Conversation
|
@bors r+ rollup=never |
📌 Commit 6a070f2 has been approved by |
⌛ Testing commit 6a070f2 with merge e3b72866246b12baf14ed74522d83a0f432e84bf... |
💔 Test failed - checks-actions |
@Mark-Simulacrum It looks like maybe #74406 needs to be backported to the beta branch. Should I just include that in this PR, or do you want to do it? Or a separate PR and then roll them up together? Let me know if I can help. |
Yeah, if you can include that here that'd be great. Alternatively you can just leave this and I can get to it in a few days, I usually do beta backports on Fridays/the weekend. |
…r=Mark-Simulacrum Set shell for github actions CI r? @pietroalbini but because this seems at worst harmless and CI is broken self approving
…roalbini ci: Set `shell: bash` as a default, remove duplicates A follow-up to rust-lang#74406, this commit merely removes the `shell: bash` lines where they were added in favor of setting defaults for *all* "run" steps in the jobs that run the tests. The changes in rust-lang#74406 were needed because of an upstream change to the `windows-2019` GitHub Actions image. Previously, the configuration worked fine without specifying `shell: bash`, but for some reason this broke with a new change that was deployed today. The preceding PR was a hotfix to get CI passing, but there was a slightly less duplicative way to specify the default shell for the jobs, which was to set the `defaults.run` option. This change applies to the `pr`, `try`, `auto`, and `auto-fallible` jobs, which are derived from the YAML-anchor `base-ci-job`. I did not apply these changes to the `master`, `try-success`, `try-failure`, `auto-success`, or `auto-failure` jobs because they have only a few steps. cc/r? @Mark-Simulacrum
📌 Commit 85f1370 has been approved by |
⌛ Testing commit 85f1370 with merge 025abffd6511a68fd5c3dad0837dd2cb4abb554b... |
@bors retry yield (p>5 if you want this landed with priority over the rollup) |
Your PR failed (pretty log, raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem. Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
@bors treeclosed- |
☀️ Test successful - checks-actions, checks-azure |
2 commits in 4f74d9b2a771c58b7ef4906b2668afd075bc8081..149022b1d8f382e69c1616f6a46b69ebf59e2dea
2020-07-08 17:13:00 +0000 to 2020-07-17 16:39:39 -0400
master
main branches" ([beta] Revert "Improve support for non-master
main branches" cargo#8503)