-
Notifications
You must be signed in to change notification settings - Fork 13.5k
Rewrite .gitattributes
CRLF ui tests into run-make tests
#142925
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
base: master
Are you sure you want to change the base?
Conversation
|
4b34c01
to
1475a51
Compare
This comment has been minimized.
This comment has been minimized.
1475a51
to
580b27c
Compare
This PR modifies cc @jieyouxu |
This comment has been minimized.
This comment has been minimized.
@rustbot author |
Reminder, once the PR becomes ready for a review, use |
580b27c
to
12e1f3d
Compare
@rustbot ready |
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.
Thanks, I do find having the BOM and \r\n
immediately visible and possible to edit to be an important property.
@bors r+ rollup |
…r=jieyouxu Rewrite `.gitattributes` CRLF ui tests into run-make tests These tests are difficult to edit. Even adding a newline to the original UI test breaks it, as all newlines in them are supposed to be `\r\n`. (Except for `trailing-carriage-return-in-string`, which only has SOME CRLF) In the run-make suite, the test is instead automatically generated with `\r\n` clearly visible, making fixes easier. Closes rust-lang#140033 Closes rust-lang#139968 r? `@jieyouxu`
Rollup of 17 pull requests Successful merges: - #124595 (Suggest cloning `Arc` moved into closure) - #139594 (Simplify `ObligationCauseCode::IfExpression`) - #141311 (make `tidy-alphabetical` use a natural sort) - #141648 ([rustdoc] Do not emit redundant_explicit_links lint if the doc comment comes from expansion) - #142255 (Add edition checks for some tests that had divergent output) - #142285 (tests: Do not run afoul of asm.validity.non-exhaustive in input-stats) - #142549 (small iter.intersperse.fold() optimization) - #142637 (Remove some glob imports from the type system) - #142647 ([perf] Compute hard errors without diagnostics in impl_intersection_has_impossible_obligation) - #142700 (Remove incorrect comments in `Weak`) - #142884 (StableMIR: Add method to retrieve body of coroutine) - #142925 (Rewrite `.gitattributes` CRLF ui tests into run-make tests) - #143001 (Rename run always ) - #143010 (Update `browser-ui-test` version to `0.20.7`) - #143015 (Add `sym::macro_pin` diagnostic item for `core::pin::pin!()`) - #143020 (codegen_fn_attrs: make comment more precise) - #143033 (Expand const-stabilized API links in relnotes) r? `@ghost` `@rustbot` modify labels: rollup
These tests are difficult to edit. Even adding a newline to the original UI test breaks it, as all newlines in them are supposed to be
\r\n
. (Except fortrailing-carriage-return-in-string
, which only has SOME CRLF)In the run-make suite, the test is instead automatically generated with
\r\n
clearly visible, making fixes easier.Closes #140033
Closes #139968
r? @jieyouxu