crater icon indicating copy to clipboard operation
crater copied to clipboard

Run experiments across parts of the Rust ecosystem!

Results 111 crater issues
Sort by recently updated
recently updated
newest added

In several different Crater runs, I've seen `pin-project-internal` jobs get killed via SIGKILL. I suspect that this is due to the build using too much memory and getting killed by...

If the old compiler successfully built a crate, but failed to build its tests, and the new compiler failed to build *the main crate*, that should be reported as a...

We were [discussing on Zulip](https://rust-lang.zulipchat.com/#narrow/stream/245100-t-compiler.2Fwg-prioritization.2Falerts/topic/I-prioritize.20.2379890.20Failed.20to.20recover.20key.20for.20type_of.20with.20.E2.80.A6/near/219529727) about some simple ideas on how to test incr compilation better. Maybe it could be nice to build crate versions N - 1 and then...

Sometimes, it would suffice to see if a code pattern exists, without having to actually run the compiler in check mode. That would be much faster, and would often provide...

When `data/github.csv` is read, only repositories with both a `Cargo.toml` and a `Cargo.lock` are tested: https://github.com/rust-lang/crater/blob/dcc54566d5ec82cabca435c0145cbd06f32d3602/src/crates/sources/github.rs#L44-L47 Based on the comment, it looks like the intention was to test repositories with...

It's common to write `@bors try @rust-timer queue` on a pull request, which will cause both bors and rust-timer to run commands. However, craterbot does not support this style of...

Right now, failed tests have output like this: Output ``` test minicrater::resource_exhaustion ... FAILED failures: ---- minicrater::resource_exhaustion stdout ---- Difference between expected and actual reports: { "categories": [], "comparison_colors": {},...

_Originally posted by @jyn514 in https://github.com/rust-lang/crater/pull/543#issuecomment-689908475_

In [this report](https://crater-reports.s3.amazonaws.com/pr-75585/index.html), several of the non-spurious regressions were actually spurious with a common theme: ``` [INFO] [stderr] Caused by: [INFO] [stderr] process didn't exit successfully: `rustc --crate-name build_script_build /opt/rustwide/cargo-home/registry/src/github.com-1ecc6299db9ec823/html5ever-0.24.1/build.rs...

Opening an issue as requested by @Mark-Simulacrum : While launching a run on a limited selection of crates [on this PR](https://github.com/rust-lang/rust/pull/73905#issuecomment-674532428) using the `crates=list:link` format [documented here](https://github.com/rust-lang/crater/blob/master/docs/bot-usage.md#available-crate-selections), the bot returned...