-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
might_permit_raw_init: also check arrays (take two) #87041
Conversation
r? @oli-obk (rust-highfive has picked a reviewer for you, use r? to override) |
@bors try |
⌛ Trying commit 4f9c4aaa674d3708cdce00fd7cd9684325405553 with merge ad8c22b50457babb1409b03fda810be4d1c3b206... |
💔 Test failed - checks-actions |
This comment has been minimized.
This comment has been minimized.
@bors try |
⌛ Trying commit 4f9c4aaa674d3708cdce00fd7cd9684325405553 with merge ecabaf78506b7a4668d42dc20268c086b93f0fad... |
☀️ Try build successful - checks-actions |
@craterbot test |
🚨 Error: failed to parse the command 🆘 If you have any trouble with Crater please ping |
@craterbot build-and-test |
🚨 Error: failed to parse the command 🆘 If you have any trouble with Crater please ping |
@craterbot run mode=build-and-test |
👌 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🚧 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🎉 Experiment
|
Looks like a big one here is |
🗑️ Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
@craterbot run mode=build-and-test |
👌 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🚧 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
@craterbot retry-report |
🛠️ Generation of the report for ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🎉 Experiment
|
So going just over the crates whose name starts with a, b, c, the failures are almost all (>80%) caused by hyper (versions before hyperium/hyper#2545) and ancient crossbeam. I added that info to #66151. It's probably not worth keeping the PR open; I am not sure if old hyper and crossbeam will ever go sufficiently out of use that we can break them entirely. |
We could backport patches to these old crates... I'm sure we can get the maintainers to do that if we do the impl work |
Patches that don't raise the MSRV might be tricky though. |
Also, tons of lockfiles will reference the old versions. So we'd also have to convince crater to do (I am pretty sure it currently doesn't do that, considering how many different versions of hyper 0.14 I saw in the crater logs.) |
That's correct, this is currently not done, somewhat intentionally -- when possible, we try to avoid breaking builds even if |
…k-Simulacrum assert_uninit_valid: ensure we detect at least arrays of uninhabited types We can't easily extend this check to *all* arrays (Cc rust-lang#87041), but it turns out the existing check already catches arrays of uninhabited types. So let's make sure it stays that way by adding them to the test.
…k-Simulacrum assert_uninit_valid: ensure we detect at least arrays of uninhabited types We can't easily extend this check to *all* arrays (Cc rust-lang#87041), but it turns out the existing check already catches arrays of uninhabited types. So let's make sure it stays that way by adding them to the test.
This is a revival of PR #79296 for a fresh Crater run