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
..
check	replace the build system with meson	2025-06-11 10:30:12 +03:00
confgen	replace the build system with meson	2025-06-11 10:30:12 +03:00
delv	Use clang-format-20 to update formatting	2025-06-25 12:44:22 +10:00
dig	Add "undefined" to +ednsflags description	2025-06-13 07:50:16 +00:00
dnssec	Use clang-format-20 to update formatting	2025-06-25 12:44:22 +10:00
named	Fix version description in a startup log message	2025-06-26 12:05:53 +02:00
nsupdate	replace the build system with meson	2025-06-11 10:30:12 +03:00
plugins	replace the build system with meson	2025-06-11 10:30:12 +03:00
rndc	Drop empty directory bin/rndc/include/	2025-06-24 12:38:37 +00:00
tests	Log assertion failures right after test result	2025-06-27 16:31:49 +02:00
tools	load the journal file if it already exists	2025-06-13 21:20:13 -07:00
meson.build	replace the build system with meson	2025-06-11 10:30:12 +03:00