rust/tests/ui/statics, branch perf-tmphttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=perf-tmp2025-09-03T13:24:49+00:00don't uppercase error messages2025-09-03T13:24:49+00:00Sasha Pourcelotsasha.pourcelot@protonmail.com2025-09-01T14:47:55+00:00urn:sha1:5c4b61b4b4b13e408b28ecc91f4f517e78e6b5e7
a more general version of https://github.com/rust-lang/rust/pull/146080.
after a bit of hacking in [`fluent.rs`](https://github.com/rust-lang/rust/blob/master/compiler/rustc_fluent_macro/src/fluent.rs), i discovered that i'm not the only one that is bad at following guidelines :sweat_smile:. this pr lowercases the first letter of all the error messages in the codebase.
(i did not change things that are traditionally uppercased such as _MIR_, _ABI_ or _C_)
i think it's reasonable to run a `@bors try` so all the test suite is checked, as i cannot run some of the tests on my machine. i double checked (and replaced manually) all the old error messages, but better be safe than sorry.
in the future i will try to add a check in `x test tidy` that errors if an error message starts with an uppercase letter.
On E0277, point at type that doesn't implement bound2025-08-22T17:55:15+00:00Esteban Küberesteban@kuber.com.ar2025-08-19T17:49:20+00:00urn:sha1:049c32797b5f797d5823cdc0e5aaeb0fd68175da
When encountering an unmet trait bound, point at local type that doesn't implement the trait:
```
error[E0277]: the trait bound `Bar<T>: Foo` is not satisfied
--> $DIR/issue-64855.rs:9:19
|
LL | pub struct Bar<T>(<Self as Foo>::Type) where Self: ;
| ^^^^^^^^^^^^^^^^^^^ unsatisfied trait bound
|
help: the trait `Foo` is not implemented for `Bar<T>`
--> $DIR/issue-64855.rs:9:1
|
LL | pub struct Bar<T>(<Self as Foo>::Type) where Self: ;
| ^^^^^^^^^^^^^^^^^
```
bless tests with new lint messages2025-08-19T19:27:10+00:00Karol Zwolakkarolzwolak7@gmail.com2025-04-28T11:47:25+00:00urn:sha1:d14b83e378c421dd09320ace833a9d47848e3046Rollup merge of #144403 - Kivooeo:issue4, r=jieyouxu2025-08-10T09:45:48+00:00Stuart CookZalathar@users.noreply.github.com2025-08-10T09:45:48+00:00urn:sha1:62b406d4b185f28828df3e0df6b1aa1f560145df
`tests/ui/issues/`: The Issues Strike Back [4/N]
Some `tests/ui/issues/` housekeeping, to trim down number of tests directly under `tests/ui/issues/`. Part of https://github.com/rust-lang/rust/issues/133895.
r? ````````@jieyouxu````````
comments2025-08-09T11:27:20+00:00KivooeoKivooeo123@gmail.com2025-07-24T14:07:20+00:00urn:sha1:16765639b30741dde85da0dbcb44c343eb82b1a2Rollup merge of #144397 - Kivooeo:issue2, r=jieyouxu2025-08-01T07:59:03+00:00Ralf Jungpost@ralfj.de2025-08-01T07:59:03+00:00urn:sha1:37ad0776acbf15b7082bcfed25132193787aab13
`tests/ui/issues/`: The Issues Strike Back [2/N]
Some `tests/ui/issues/` housekeeping, to trim down number of tests directly under `tests/ui/issues/`. Part of https://github.com/rust-lang/rust/issues/133895.
r? ``@jieyouxu``
comments2025-07-31T16:25:49+00:00KivooeoKivooeo123@gmail.com2025-07-24T12:22:54+00:00urn:sha1:a4a5bf5a71bd0c3fb52a28f81d88ce1755b3bc30Rollup merge of #144356 - GuillaumeGomez:gcc-ignore-tests, r=jieyouxu2025-07-26T06:15:08+00:00Trevor Grosst.gross35@gmail.com2025-07-26T06:15:08+00:00urn:sha1:6b1b68f4ee9314e4286f98d38f8b0f3cde3938c5
Add `ignore-backends` annotations in failing GCC backend ui tests
Follow-up of https://github.com/rust-lang/rust/pull/144125.
In the GCC backend, we don't support all ui tests yet and we have a list of tests we currently ignore available [here](https://github.com/rust-lang/rustc_codegen_gcc/blob/master/tests/failing-ui-tests.txt).
This PR adds the `ignore-backends` annotations to the corresponding ui tests.
The second commit is a fix to compiletest, complaining about `ignore-backends`.
r? ```@jieyouxu```
moved 34 tests to organized locations2025-07-25T10:34:28+00:00KivooeoKivooeo123@gmail.com2025-07-24T13:29:09+00:00urn:sha1:90bb5cacb5c1a5fe20ba821d28e7eb7a21e35d09moved 35 tests to organized locations2025-07-24T12:15:36+00:00KivooeoKivooeo123@gmail.com2025-07-24T12:15:36+00:00urn:sha1:d636a6590ce1429ff011e04bb0b4d393dc382226