-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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 error annotations in UI tests #11249
Conversation
r? @blyxyas (rustbot has picked a reviewer for you, use r? to override) |
4cefbcf
to
3723670
Compare
Fixed the very weird differences between rustc's ui tests and clippy's. Also correctly handled comments length. Should be ready now. |
r? @llogiq |
☔ The latest upstream changes (presumably #11250) made this pull request unmergeable. Please resolve the merge conflicts. |
3723670
to
79814c7
Compare
Fixed merge conflict (this PR is going to be very merge conflict prone ><). |
☔ The latest upstream changes (presumably #11269) made this pull request unmergeable. Please resolve the merge conflicts. |
@@ -12,27 +12,46 @@ fn main() { | |||
const Z: u32 = 0; | |||
let u: u32 = 42; | |||
u <= 0; | |||
//~^ ERROR: this comparison involving the minimum or maximum element for this type con |
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.
If these could use //~
instead for ones that are a single error then that'd be great, would require tons of manual work though...
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.
I'd prefer to keep having the message level. The goal is to ensure both that the message content and the message level don't get updated unnoticed.
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.
I mean having it inline, not omitting the level, like
u <= 0; //~ ERROR: etc
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.
Oh sorry, misunderstood. So yes, a lot of manual work which I don't have time for, sorry about that... Do you mind if we keep it this way?
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.
I don't, it's fine as is. Maybe we can update the script you used at some point to do this instead
79814c7
to
6dae4cf
Compare
Fixed merge conflicts. Would be nice if it didn't take too long to merge if possible. ^^' |
Nominating to see if everyone's onboard with this in 2 weeks. If we are, then this can probably be merged fine. (Though it'll result in a ton of conflicts, how fun!) Alternatively, we could also create a poll in a new thread so it doesn't take 2 weeks. I think everyone's onboard with this already so it may not be worth the time. How does that sound? |
☔ The latest upstream changes (presumably #11316) made this pull request unmergeable. Please resolve the merge conflicts. |
I'll keep it up-to-date as much as possible (for example, gonna fix the current conflict :D ). |
6dae4cf
to
4353167
Compare
☔ The latest upstream changes (presumably #11239) made this pull request unmergeable. Please resolve the merge conflicts. |
0fcad09
to
ab5bfee
Compare
☔ The latest upstream changes (presumably #11336) made this pull request unmergeable. Please resolve the merge conflicts. |
r=me once we have everyone on board next Tuesday shortly after 5pm CEST. Perhaps rebase during the hours before, then we can merge quickly without requiring multiple rebases. |
Noted! Please ping me when I can make the final rebase. |
Hey @GuillaumeGomez ! We've decided to merge this, so r=me with rebase @bors delegate+ |
✌️ @GuillaumeGomez, you can now approve this pull request! If @llogiq told you to " |
I believe this should also change mode to @oli-obk, can you confirm this is what we want? Or would we need a new mode? |
Do you wan the new mode to be set in this PR directly or in a follow-up one? |
Follow-up, once the book is updated |
ab5bfee
to
f467012
Compare
Nope, this is the right setting |
@bors r=Centri3,llogiq |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
I'll send the follow-up PR to turn the setting on in the next days. |
As discussed on zulip, this PR adds missing error annotations in UI tests.
I used this script to generate them:
Then ran
cargo uibless
.changelog: none