-
Notifications
You must be signed in to change notification settings - Fork 13.3k
[beta] try to work around type normalization regression #78845
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
r? @sfackler (rust_highfive has picked a reviewer for you, use r? to override) |
|
@bors try I don't think a crater run here is necessary -- checking the one crate locally shouldn't be too hard -- but having artifacts for easier testing is nice :) |
⌛ Trying commit f20775a with merge 9898131620287f170f82e89c851e0d7fc8436424... |
It does have a command to run it for a single crate, is that still overkill? |
☀️ Try build successful - checks-actions |
Color me surprised, it worked.
|
@bors r+ rollup=never Can you also post an equivalent PR against master? |
📌 Commit f20775a has been approved by |
@bors p=10 |
☀️ Test successful - checks-actions |
This just removes the offending lines that trigger #78139. I have doubts that this will actually solve the issue but it's simple enough to try.
This PR needs a crater run for the failing crate.