Source: debhelper
Version: 13.20
Severity: wishlist
Hello, in Bug#918066, Jeremy Bicha suggested to print the test log at
least when the build tests fail.
On Wed, 2 Jan 2019 17:57:26 -0500 Jeremy Bicha <jbi...@debian.org> wrote:
I think it would be appropriate if debhelper's meson backend would > include in
the build logs the content of
$(CURDIR)/obj-$(DEB_HOST_GNU_TYPE)/meson-logs/testlog.txt at least
when the build tests fail. This can help diagnose test failures
(especially on obscure architectures.)
I think this is encouraged by Debian Policy ยง4.9's paragraph about the
build being as verbose as possible.
Meson 1.5.0 (released on 10 July 2024) introduced a "--interactive" flag
to "meson test", which allows to directly connect stdout, stdin and
stderr to the running shell. This would print the whole test output in
the logs. Wouldn't it be more in line with what is recommended in the
policy?
This could also simplify the related code in debhelper.
I tested it myself with the following rule and it works as expected:
override_dh_auto_test:
dh_auto_test --buildsystem=meson+ninja -- --interactive
--
Nicolas Peugnet
