[WIP] Test if clippy got much slower over the last few days #4712
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Closed and reopend to trigger rebuild. |
|
Note that Clippy is not building right now due to rust-lang/rust#65647. The integration tests don't fail even if they should? |
Should be fixed in #4675 |
The aid is to check if clippy got much slower over the last few days. But not because of rust-lang#4703.
tesuji
force-pushed
the
test-if-clippy-got-much-slow
branch
from
953de1f to
1e9e62e
Compare
It seems that clippy is really slow on non-git project
This reverts commit 74d4550.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The aid is to check if clippy got much slower over the last few days.
And check if its cause is #4703.
changelog: none