RE: [PATCH v2] ci: improve logging of unit tests runs

Marat Khalili
2026-01-19T13:21:02Z

> -----Original Message-----
> From: Bruce Richardson <bruce.richardson@intel.com>
> Sent: Monday 19 January 2026 11:56
> To: dev@dpdk.org
> Cc: Bruce Richardson <bruce.richardson@intel.com>; Aaron Conole <aconole@redhat.com>
> Subject: [PATCH v2] ci: improve logging of unit tests runs
>
> To help track down issues reported by CI test runs, add some additional
> meson flags to the run of the fast-tests:
>
> --no-stdsplit:
> keep the stdout and stderr output interleaved, rather
> than separated in the logs, to make following what is happening during
> a test run easier.
> --print-errorlogs:
> when an error with a unit test does occur, output to the terminal the
> last N lines of output. This allows us to see inline what may have
> failed without always needing to check log files.
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
> V2: Drop max-lines flag, since it's only introduced in very recent meson
> versions.
> ---
> .ci/linux-build.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/.ci/linux-build.sh b/.ci/linux-build.sh
> index ceead259f3..084d9642fc 100755
> --- a/.ci/linux-build.sh
> +++ b/.ci/linux-build.sh
> @@ -218,7 +218,7 @@ fi
> if [ "$RUN_TESTS" = "true" ]; then
> failed=
> configure_coredump
> - sudo meson test -C build --suite fast-tests -t 3 || failed="true"
> + sudo meson test -C build --suite fast-tests -t 3 --no-stdsplit --print-errorlogs || failed="true"
> catch_coredump
> catch_ubsan DPDK:fast-tests build/meson-logs/testlog.txt
> check_traces
> --
> 2.51.0

Acked-by: Marat Khalili <marat.khalili@huawei.com>

(Using both flags in our local CI for long time.)