Nicki Křížek fcf31417dd Log assertion failures right after test result ... The extra messages are typically traceback from assertion failures. Previously, they'd be printed only after all individual test case results have been printed. That made it difficult to pair the traceback to the failing test in some cases, as the node information (aka test name) might not always be present. Instead, log any extra messages related to a particular test failure directly after reporting its result, making the failure details more readily available and easy to connect with a particular test case.		2025-06-27 16:31:49 +02:00
..
startperf	Reformat shell scripts with shfmt	2023-10-26 10:23:50 +02:00
system	Log assertion failures right after test result	2025-06-27 16:31:49 +02:00
testdata/wire	move all optional tests from bin/tests to bin/tests/optional	2018-03-09 14:12:47 -08:00
.gitignore	Move environment variables from conf.sh to pytest	2024-05-09 17:08:08 +02:00
meson.build	replace the build system with meson	2025-06-11 10:30:12 +03:00
test_client.c	Move the library init and shutdown to executables	2025-02-22 16:19:00 +01:00
test_server.c	Move the library init and shutdown to executables	2025-02-22 16:19:00 +01:00