rust/tests/ui/test-attrs, branch cargo_updatehttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=cargo_update2025-09-26T13:33:48+00:00Ignore more failing ui tests for GCC backend2025-09-26T13:33:48+00:00Guillaume Gomezguillaume1.gomez@gmail.com2025-09-26T11:59:06+00:00urn:sha1:a535c7be5444fb6584eecc99f53e6cdb710ff70fAdd more docs to templates for attrs with incorrect arguments2025-08-11T17:02:32+00:00Esteban Küberesteban@kuber.com.ar2025-08-11T17:02:32+00:00urn:sha1:32ee26c625e8fbb7a3aa56788cbb352f04491964mbe: In error messages, don't assume attributes are always proc macros2025-08-08T17:35:47+00:00Josh Triplettjosh@joshtriplett.org2025-07-28T10:00:24+00:00urn:sha1:2054a0c56b063c195d316e4ff44d0c9f8ad2c012
Now that `macro_rules` macros can define attribute rules, make sure
error messages account for that.
Rollup merge of #143808 - JonathanBrouwer:should_panic_parser, r=jdonszelmann2025-08-07T10:49:40+00:00Stuart CookZalathar@users.noreply.github.com2025-08-07T10:49:40+00:00urn:sha1:995ca3e532b48b689567533e6b736675e38b741e
Port `#[should_panic]` to the new attribute parsing infrastructure
Ports `#[should_panic]` to the new attribute parsing infrastructure for https://github.com/rust-lang/rust/issues/131229#issuecomment-2971351163
r? ```@jdonszelmann```
Print thread ID in panic message if thread name is unknown2025-08-06T23:59:47+00:00Trevor Grosstmgross@umich.edu2023-09-11T04:59:31+00:00urn:sha1:289fe36d373c5a13fa7f1b93f39ff88425ab2351
`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 '<unnamed>' panicked at src/main.rs:3:5:
explicit panic
To something like this:
thread '<unnamed>' (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.
Changes to the tests for the `#[should_panic]` port2025-08-06T19:38:00+00:00Jonathan Brouwerjonathantbrouwer@gmail.com2025-07-11T16:37:00+00:00urn:sha1:4281e05a209a15a4b2de63ea5a552fc59f8bd0f1
Signed-off-by: Jonathan Brouwer <jonathantbrouwer@gmail.com>
Rollup merge of #142214 - Kivooeo:tf9, r=jieyouxu2025-06-29T10:29:54+00:00Guillaume Gomezguillaume1.gomez@gmail.com2025-06-29T10:29:54+00:00urn:sha1:15b227f71532fffcab7663ffc1b2711e955a02de
`tests/ui`: A New Order [9/N]
Some `tests/ui/` housekeeping, to trim down number of tests directly under `tests/ui/`. Part of rust-lang/rust#133895.
cleaned up some tests2025-06-28T12:04:16+00:00KivooeoKivooeo123@gmail.com2025-06-08T19:49:05+00:00urn:sha1:f4502b8f0eeb0e2f078745cfbbe41b5763be9449cleaned up some tests2025-06-08T06:25:09+00:00KivooeoKivooeo123@gmail.com2025-06-07T11:17:21+00:00urn:sha1:85ce9ee481a56bcabaa9480cfc0e2b420e4f1807Remove backticks from `ShouldPanic::YesWithMessage`'s `TrFailedMsg`2025-04-28T19:40:29+00:00Lieselotte52315535+she3py@users.noreply.github.com2025-04-28T19:40:29+00:00urn:sha1:55a419f444378afb5eceb361959fa57eefce2be1