-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Enable internal feature when testing Clippy #104007
Conversation
👍 seems good - I remember this having interactions with #96798, but I don't know when I'll get back to that PR, so this is fine in the meantime. |
…p1995 Update Clippy r? `@Manishearth` Sorry for taking so long. There were so many blockers and so little time. This situation should be mitigated with rust-lang#104007 in the future.
@bors r+ rollup=iffy (clippy isn't tested in PR CI) |
📌 Commit 075f4c49a30fede0b7ed91f56a4928ef717ba224 has been approved by It is now in the queue for this repository. |
⌛ Testing commit 075f4c49a30fede0b7ed91f56a4928ef717ba224 with merge 4d35d8785bbfdb2ac53632555885fde767afaa9d... |
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
Clippy has internal lints, that only get build and tested, when the `internal` feature is enabled. Those tests are just regular UI tests, but split out from the normal UI tests, because they usually don't have to be touched when changing something in Clippy. However, changes to Rust internals often require updates of the internal lints, just as for the Rest of the Clippy codebase. Currently I fix this fallout during the sync. But this can lead to sync blockers in rare occasions.
075f4c4
to
7391e39
Compare
Some changes occurred in src/tools/clippy cc @rust-lang/clippy |
The order of the lint messages in
seems to be different between the Clippy and the Rust repo. This is weird. 🤔 @rustbot ready |
The job Click to see the possible cause of the failure (guessed by this bot)
|
…p1995 Update Clippy r? `@Manishearth` Sorry for taking so long. There were so many blockers and so little time. This situation should be mitigated with rust-lang#104007 in the future.
☔ The latest upstream changes (presumably #105827) made this pull request unmergeable. Please resolve the merge conflicts. |
I don't have time for looking into the issue here sadly.. And since I don't want this to get in the way of the other work done about x.py+clippy, I'll close this for now and will get back to it once the other work is done. |
Hm, the asserts are most likely caused by spans of length 0 or spans that point at code segments that don't exist. This causes an ice with debug assertions. |
The issue was mainly that lint messages in internal UI tests were swapped. But I'm currently seeing them flipping around in every other clippy sync... The ICE is expected (used to be an easter egg in Clippy1 but is now behind the Footnotes
|
Sorry, I mean the
one ^^ |
That might just be a weird backtrace because we |
Hmm right, this seems to be a different problem. |
Clippy has internal lints, that only get build and tested, when the
internal
feature is enabled. Those tests are just regular UI tests, but split out from the normal UI tests, because they usually don't have to be touched when changing something in Clippy. However, changes to Rust internals often require updates of the internal lints, just as for the Rest of the Clippy codebase. Currently I fix this fallout during the sync. But this can lead to sync blockers in rare occasions.Blocked on #104006, because it will fail Clippy build/tests until that is merged.
This will prevent fallouts like the one in #103603
r? @jyn514