-
Notifications
You must be signed in to change notification settings - Fork 13.3k
[beta] Remove statement that was forgotten when backporting #94596 #95093
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
Conversation
|
This comment has been minimized.
This comment has been minimized.
b50af5a
to
3191ede
Compare
Thanks! It does indeed seem plausible order was wrong - I don't think I saw rebase errors around this but could just be git producing wrong results in wrong order. It might be nice to see if we can add tests (to master). @bors r+ rollup=never since these changes were already backport approved. |
📌 Commit 3191ede has been approved by |
⌛ Testing commit 3191ede with merge 6c380750e1c8098b3d8eaa80ba50d9bf3bf8590e... |
💔 Test failed - checks-actions |
The job Click to see the possible cause of the failure (guessed by this bot)
|
Hmm... strange. Wtf is going on here. Will look into it.
|
Ah, glad it wasn't my fault.. |
⌛ Testing commit 3191ede with merge 771dddd1a55d4b5cc2dda5cf1b4f7b8c763d9497... |
💔 Test failed - checks-actions |
Hm, seems like a spurious failure. Can someone bors-retry? |
@bors retry x86_64-apple-2: The hosted runner: GitHub Actions 47 lost communication with the server. |
☀️ Test successful - checks-actions |
This
if
statement was introduced in #94438, then removed in #94596. Both of these PRs were beta-backported in #94933, but I think there was a mistake in the order they were applied or this removal was overlooked. I think this fixes the remaining issues referenced in #94511 (comment).Not sure this is the correct way to put something up for beta-backport, but the PR is at least open so it can be referenced and the commit can be cherry-picked. Feel free to close this PR.
r? @Mark-Simulacrum
cc: #94511