-
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
Crater runs for 1.48 #77970
Comments
@craterbot run name=beta-1.48-1 start=1.47.0 end=beta-2020-10-09 mode=build-and-test cap-lints=warn p=10 |
👌 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
@craterbot run name=beta-1.48-rustdoc-1 start=1.47.0 end=beta-2020-10-09 mode=rustdoc cap-lints=warn p=5 |
👌 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 ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🎉 Experiment
|
I triaged the build failures from the crater run, but ran out of energy to open the ~245 test failures. I personally suspect many of them to be the uninitialized checking getting more stringent; I plan to finish this up later today hopefully. Opened/tagged:
There's also a bunch of failures in build scripts due to old versions of crossbeam-epoch having UB around mem::uninitialized, but that's intentional/won't fix. I believe those folks should be a cargo update away from fixing the failure. |
There's a bunch of segfaults/aborts etc -- 49 of them -- that I have not yet tried to diagnose, see https://gist.github.com/Mark-Simulacrum/d0759db08cd0528ae2762c1aecf04c37 for a list of log files. Beyond that I've triaged the rest of the test failures and those look good. I think for these it would be good to re-run crater on the subset and see how many of them are still present (which should be quick), I'll look at doing that shortly. |
@craterbot run name=beta-1.48-2-subset start=1.47.0 end=beta-2020-10-16 mode=build-and-test cap-lints=warn p=10 crates=list:https://gist.githubusercontent.com/Mark-Simulacrum/ecfa4deb6ba7151067d71269ba567f30/raw/c0375bdc243814a9af60f0ff19ada599091ce8ad/gistfile1.txt Hopefully this works... |
🚨 Error: missing desired crates: {"https://gist.githubusercontent.com/Mark-Simulacrum/ecfa4deb6ba7151067d71269ba567f30/raw/c0375bdc243814a9af60f0ff19ada599091ce8ad/gistfile1.txt"} 🆘 If you have any trouble with Crater please ping |
Huh. Not sure what's wrong there. @pietroalbini would you be able to find some time to take a look? I don't think it's super urgent but would be good to have this cycleish. |
@craterbot run name=beta-1.48-2-subset start=1.47.0 end=beta-2020-10-16 mode=build-and-test cap-lints=warn p=10 crates=https://gist.githubusercontent.com/Mark-Simulacrum/ecfa4deb6ba7151067d71269ba567f30/raw/c0375bdc243814a9af60f0ff19ada599091ce8ad/gistfile1.txt |
👌 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
|
The first segfault ( This is easier to see if the tests are run with |
🎉 Experiment
|
See this hackmd for the previous regression analysis of #71274. The vast majority of these cases has semver-compatible updates (in particular, everything caused by linked-hash-map), but I am not sure if crater has picked those up -- in the past I had trouble with crater using a broken version of a crate even when a fixed version was available. We focused on crates though and mostly skipped GH repositories; in my prior experience, 100% of those regressions were one-off repositories of unmaintained code (things like advent of code) or the cause was in some dependency on crates.io, so there was little expected payoff from going over all of those as well. So there's nothing on |
Note: Please do not conduct triage on these runs without discussing how to do so with a release team member first. Thanks!
The text was updated successfully, but these errors were encountered: