-
Notifications
You must be signed in to change notification settings - Fork 1.6k
rustup and compile-fail -> ui test move #1520
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
Conversation
Going to bed. Feel free to take over. |
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.
While I love the idea to have UI tests I wonder whether these make sense for all the tests.
If it does, why does rustc itself still bother with compile-fail tests?
CONTRIBUTING.md
Outdated
Clippy uses UI tests. UI tests check that the output of the compiler is exactly as expected. | ||
Of course there's little sense in writing the output yourself or copying it around. | ||
Therefore you can simply run `tests/ui/update-all-references.sh` and check whether | ||
the output looks as you expect with `git diff`. Commit all `.stderr` files, too. |
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.
👍 Nice of you to update that!
I'd just say “Commit all *.stderr
files” because I though for a moment “why the hell those are hidden files?”.
They are moving to just checking true compilation failures that abort the program. Everything else is a ui test. |
r+ modulo |
“remove all //~ from tests” → the end of an era 😢 😄 |
fixes #1519