rust/tests/run-make/libtest-json, branch master

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.

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

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

Port `run-make/libtest-json/validate_json.py` to Rust

2024-08-17T08:15:38+00:00

This is a trivial Python script that simply tries to parse each line of stdin (i.e. the test process output) as JSON, to verify that the overall output is JSON Lines. We can perform the same check directly in `rmake.rs` using `serde_json`.

Port `run-make/libtest-json` to rmake

2024-08-13T03:27:15+00:00

Change default panic handler message format.

2023-07-29T09:42:50+00:00

Add needs-unwind annotations to tests that need stack unwinding

2023-05-02T12:07:55+00:00

ignore failing cross-compiled run-make tests

2023-03-30T13:46:31+00:00

`run-make-fulldeps` is never cross-compiled, so a lot of these tests never accounted for --target. Ignore them when cross-compiling for now.

Move almost all run-make-fulldeps to run-make

2023-03-30T12:34:55+00:00

They pass fine.