rust/tests/ui/treat-err-as-bug, branch try-perf

Print thread ID in panic message if thread name is unknown

2025-08-06T23:59:47+00:00

`panic!` does not print any identifying information for threads that are unnamed. However, in many cases, the thread ID can be determined. This changes the panic message from something like this: thread '' panicked at src/main.rs:3:5: explicit panic To something like this: thread '' (0xff9bf) panicked at src/main.rs:3:5: explicit panic Stack overflow messages are updated as well. This change applies to both named and unnamed threads. The ID printed is the OS integer thread ID rather than the Rust thread ID, which should also be what debuggers print.

const-eval error: always say in which item the error occurred

2025-06-07T11:42:30+00:00

also adjust the wording a little so that we don't say "the error occurred here" for two different spans

Clarify why we are talking about a failed const eval at a random place

2025-06-02T15:37:15+00:00

Use the informative error as the main const eval error message

2025-06-02T15:37:15+00:00

compiletest: Support matching on non-json lines in compiler output

2025-05-04T15:27:45+00:00

and migrate most of remaining `error-pattern`s to it.

compiletest: Require `//~` annotations even if `error-pattern` is specified

2025-04-03T08:08:55+00:00

Remove attribute `#[rustc_error]`

2025-03-29T22:32:21+00:00

Remove all dead files inside tests/ui/

2025-01-27T01:28:04+00:00

Try to write the panic message with a single `write_all` call

2025-01-01T14:58:29+00:00

Remove the `-test` suffix from normalize directives

2024-12-27T08:58:16+00:00