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

[Patrick Robb]

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 at redhat.com> wrote:

> Bruce Richardson <bruce.richardson at 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 at 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 at 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.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mails.dpdk.org/archives/ci/attachments/20260120/b691a701/attachment.htm>