-
Notifications
You must be signed in to change notification settings - Fork 92
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
Add a new clippy
mode to crater to test lint regressions
#391
Conversation
0681269
to
c207b79
Compare
clippy
mode to crater to test crater regressionsclippy
mode to crater to test lint regressions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything except the mount flag change looks great! Thank you!
I'd prefer not to pass --security-opt=label:disable
to Docker though (we're basically running untrusted code and every bit of extra security helps). An alternative is to store the toolchain name on the filesystem urlencoded with a custom encode set (like we do during report generation) that includes :
in it.
This commit also adds a method, `Toolchain::install_rustup_component` to install a rustup componenet on the given toolchain.
The test runs crater in `clippy` mode and compares `stable` with `stable+rustflags=-Dclippy::all` so that a regression will appear when clippy would emit a warning on a crate. Also adds a new local crate which compiles succesfully but causes clippy to emit a warning.
e859fb3
to
1d89103
Compare
1d89103
to
3985d0c
Compare
I reverted the changes to There's some crossover here with Windows support, so I chose to escape all characters which are invalid as part of a Windows path, not just |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great, thanks!
clippy
mode to crater to test lint regressionsclippy
mode to crater to test lint regressions
@bors r+ |
📌 Commit 3985d0c has been approved by |
Add a new `clippy` mode to crater to test lint regressions Resolves #388. This adds a new mode, `clippy`, to crater which runs clippy on crates (duh :). I had to add some new options to minicrater, as well as change the invocation of `docker create`. See the commit messages for more info. This is still a work in progress as I'd like to add some documentation for the feature, but should be enough for a meaningful review.
💔 Test failed - checks-travis |
💔 |
Add a new `clippy` mode to crater to test lint regressions Resolves #388. This adds a new mode, `clippy`, to crater which runs clippy on crates (duh :). I had to add some new options to minicrater, as well as change the invocation of `docker create`. See the commit messages for more info. This is still a work in progress as I'd like to add some documentation for the feature, but should be enough for a meaningful review.
WTF bors. @bors r- retry |
Whoops, I forgot to add the results of the |
Okay, should be good to go now. |
Thanks! @bors r+ |
📌 Commit 42174eb has been approved by |
Add a new `clippy` mode to crater to test lint regressions Resolves #388. This adds a new mode, `clippy`, to crater which runs clippy on crates (duh :). I had to add some new options to minicrater, as well as change the invocation of `docker create`. See the commit messages for more info. This is still a work in progress as I'd like to add some documentation for the feature, but should be enough for a meaningful review.
☀️ Test successful - checks-travis, status-appveyor |
Add documentation for new clippy mode Instructions for populating `rustflags` are included elsewhere in the docs, so this single line should suffice. This should have been included in #391 (whoops).
Resolves #388.
This adds a new mode,
clippy
, to crater which runs clippy on crates (duh :).I had to add some new options to minicrater, as well as change the invocation of
docker create
. See the commit messages for more info.This is still a work in progress as I'd like to add some documentation for the feature, but should be enough for a meaningful review.