about summary refs log tree commit diff
path: root/tests/run-make/libtest-junit
AgeCommit message (Collapse)AuthorLines
2025-01-01Try to write the panic message with a single `write_all` callJohn Kåre Alsaker-2/+2
2024-09-05tests: use renamed `stdin_buf`许杰友 Jieyou Xu (Joe)-1/+1
2024-08-22Advise against removing `run-make/libtest-junit/validate_junit.py`Zalathar-0/+10
Trying to get rid of this Python script looks tempting, because it's currently the only Python script in the whole `run-make` suite that we actually run. But getting rid of it would require pulling in a Rust crate to parse XML instead, and that's probably not worth the extra hassle for a relatively-minor test.
2024-08-13Port `run-make/libtest-junit` to rmakeZalathar-20/+31
2024-03-25Add needs-unwind annotations to a couple of testsbjorn3-0/+1
2023-07-29Change default panic handler message format.Mara Bos-2/+2
2023-06-16Apply changes to fix python linting errorsTrevor Gross-1/+1
2023-04-28junit: fix typo in comment and don't include output for passes when not ↵Augie Fackler-1/+1
requested
2023-04-21junit: also include per-case stdout in xmlAugie Fackler-2/+2
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-21libtest: add tests for junit output formatAugie Fackler-0/+56
I'm about to make some changes here, and it was making me uneasy to modify the output format without test coverage.