| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2025-08-06 | Print thread ID in panic message if thread name is unknown | Trevor Gross | -5/+5 | |
| `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. | ||||
| 2024-03-06 | compiletest: Add a `//@ needs-threads` directive | Alex Crichton | -1/+1 | |
| This commit is extracted from #122036 and adds a new directive to the `compiletest` test runner, `//@ needs-threads`. This is intended to capture the need that a target must implement threading to execute a specific test, typically one that uses `std::thread`. This is primarily done for WebAssembly targets which currently do not have threads by default. This enables transitioning a lot of `//@ ignore-wasm*`-style ignores into a more self-documenting `//@ needs-threads` directive. Additionally the `wasm32-wasi-preview1-threads` target, for example, does actually have threads, but isn't tested in CI at this time. This change enables running these tests for that target, but not other wasm targets. | ||||
| 2024-02-16 | [AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives | 许杰友 Jieyou Xu (Joe) | -4/+4 | |
| 2023-07-29 | Change default panic handler message format. | Mara Bos | -1/+2 | |
| 2023-01-11 | Move /src/test to /tests | Albert Larsan | -0/+13 | |
