[PATCH] ci: improve logging of unit tests runs

[PATCH] ci: improve logging of unit tests runs

[Bruce Richardson]

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.
--max-lines=20:
  limit output on error to just 20 lines, to avoid overloading the
  user with superfluous output.

Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
 .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..f733da7758 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 --max-lines=20 || failed="true"
     catch_coredump
     catch_ubsan DPDK:fast-tests build/meson-logs/testlog.txt
     check_traces
-- 
2.51.0

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

[Bruce Richardson]

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

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

[Marat Khalili]

> -----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.)

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

[Aaron Conole]

Bruce Richardson <bruce.richardson@intel.com> writes:

> 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.
> ---

Thanks for working on this.  I guess when we bump our meson support
version we could re-introduce the max-lines flag (looks like it was
added in 1.5.0 based on reading the notes).

Acked-by: Aaron Conole <aconole@redhat.com>

CC'ing Patrick and the CI list - just in case any of the labs have any
special processing when they pull error logs.

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

[Patrick Robb]

[-- Attachment #1: Type: text/plain, Size: 1673 bytes --]

Thanks Aaron, Bruce,

Yes, we have our own build and unit test scripts in Jenkins that we should
update to align with the above.

Matt, please go ahead and add these flags and send a jenkins PR. The one
exception to this will be the special pipeline for running unit tests on
aarch32, since that needs to be run from dpdk-test directly, instead of
using meson test. So, you don't need to modify that aarch32 pipeline.

On Tue, Jan 20, 2026 at 8:19 AM Aaron Conole <aconole@redhat.com> wrote:

> Bruce Richardson <bruce.richardson@intel.com> writes:
>
> > 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.
> > ---
>
> Thanks for working on this.  I guess when we bump our meson support
> version we could re-introduce the max-lines flag (looks like it was
> added in 1.5.0 based on reading the notes).
>
> Acked-by: Aaron Conole <aconole@redhat.com>
>
> CC'ing Patrick and the CI list - just in case any of the labs have any
> special processing when they pull error logs.
>
>

[-- Attachment #2: Type: text/html, Size: 2353 bytes --]

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

[David Marchand]

On Mon, 19 Jan 2026 at 12:56, Bruce Richardson
<bruce.richardson@intel.com> wrote:
>
> 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>

Thanks, logs are easier to read like this.

Applied.


-- 
David Marchand