From: Aaron Conole <aconole@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, Patrick Robb <probb@iol.unh.edu>, ci@dpdk.org
Subject: Re: [PATCH v2] ci: improve logging of unit tests runs
Date: Tue, 20 Jan 2026 08:19:13 -0500 [thread overview]
Message-ID: <f7ttswgxvzi.fsf@redhat.com> (raw)
In-Reply-To: <20260119115607.225929-1-bruce.richardson@intel.com> (Bruce Richardson's message of "Mon, 19 Jan 2026 11:56:07 +0000")
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.
next prev parent reply other threads:[~2026-01-20 13:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 10:41 [PATCH] ci: improve logging of unit tests runs Bruce Richardson
2026-01-19 11:56 ` [PATCH v2] " Bruce Richardson
2026-01-19 13:20 ` Marat Khalili
2026-01-20 13:19 ` Aaron Conole [this message]
2026-01-20 16:24 ` Patrick Robb
2026-01-21 9:14 ` David Marchand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f7ttswgxvzi.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=probb@iol.unh.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.