taskcluster-crater
taskcluster-crater copied to clipboard
An idea. Many regressions are caused by `deny(warnings)`. Detect them, and separate them in the regression report.
Each crater run fetches many dependencies that are unused: - Optional `dependencies` — not needed for `cargo build` - All `dev-dependencies` — not needed for `cargo build`
It seems like crater uses dev-dependencies in establishing root/non-root relations for regressions, but since dev-dependencies are unused, this leads to real root regressions moving into the "non-root" category.