-
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
Fail if I/O error occurs during testing #72089
Fail if I/O error occurs during testing #72089
Conversation
@bors rollup=never in case we're silently accepting this somehow on CI; if so we'll need a more complicated fix |
@bors r+ p=100 |
📌 Commit a5ba752 has been approved by |
⌛ Testing commit a5ba752 with merge 1847bb88796e9f2a760095938f07bcf4db12212e... |
Nominating for this change to be backported to beta, as it fixed a really bad bug in our test harness. |
☀️ Test successful - checks-actions, checks-azure |
👀 Test was successful, but fast-forwarding failed: 422 Update is not a fast forward |
What. @bors retry |
⌛ Testing commit a5ba752 with merge 81bc86984d5bf63c09d43ec7db6cc0e7b0dc5949... |
💔 Test failed - checks-actions |
What?! @bors retry -- shouldn't be related to this |
☀️ Test successful - checks-actions, checks-azure |
@rustbot modify labels: beta-accepted Discussed this in the infra team meeting, accepting for backport. |
[beta] Rollup backports This includes: * Fail if I/O error occurs during testing rust-lang#72089 * Fix hang in lexical_region_resolve rust-lang#72087 * Fix E0284 to not use incorrect wording rust-lang#71960 * Bump pulldown-cmark rust-lang#71682
First known case of this is in #72053 (comment) but may have happened before then.
r? @pietroalbini