crater
crater copied to clipboard
rust-lang
Run experiments across parts of the Rust ecosystem!
Currently only PR numbers are displayed on https://crater.rust-lang.org/, which isn't very helpful to tell at a glance how far down in the queue a specific pull request is.
There's a large number of crates out there which are Windows specific, so it is essential that crater be able to test those crates. ## CLI usage on Windows *...
It could be very interesting for crater to collect compiler performance metrics when testing two versions of the compiler. While performance gains or losses for one particular crate might not...
Broken crates (i.e., crates that do not build on the current version of the compiler) are currently only manually black listed (and this happens rarely). Some crates are simply broken...
It's not very visible to outside people whether a particular crate is being tested by Crater. Providing badges people can put on READMEs that say whether a particular crate builds...
When doing test runs for #399 on a D4v3 Azure instance, I occasionally observed some [spurious regressions/fixes](https://ecstatic-morse.github.io/crater/top-100_2/default/). These appear to be caused by an error in the docker daemon which...
 It's not immediately obvious that the left-hand side is "before" and the right-hand side is "after". Putting labels above each column would make this clearer.
I recently found that Crater was picking up my project as well from Github, but unfortunately it was failing on my crate. My crate uses a virtual manifest, which means...
It's often useful to distinguish compiler ICEs, which are bug by definition, from compiler errors, which are usually not bugs. This is especially true when performing rustdoc crater runs, as...
At the moment the target directories used by Crater don't have a size limit, so they reach hundreds of gigabytes in size, forcing us to have 4TB disks on the...
