rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2025-08-06	Print thread ID in panic message if thread name is unknown	Trevor Gross	-1/+1
	`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.
2025-01-01	Try to write the panic message with a single `write_all` call	John Kåre Alsaker	-1/+1

2023-07-29	Change default panic handler message format.	Mara Bos	-1/+1

2023-04-28	junit: fix typo in comment and don't include output for passes when not ↵	Augie Fackler	-1/+1
	requested
2023-04-21	junit: also include per-case stdout in xml	Augie Fackler	-1/+1
	By placing the stdout in a CDATA block we avoid almost all escaping, as there's only two byte sequences you can't sneak into a CDATA and you can handle that with some only slightly regrettable CDATA-splitting. I've done this in at least two other implementations of the junit xml format over the years and it's always worked out. The only quirk new to this (for me) is smuggling newlines as to avoid literal newlines in the output.
2023-04-21	libtest: add tests for junit output format	Augie Fackler	-0/+1
	I'm about to make some changes here, and it was making me uneasy to modify the output format without test coverage.