ci: improve logging of unit tests runs
PATCH 1/1 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.
--max-lines=20:
limit output on error to just 20 lines, to avoid overloading the user with superfluous output.
--- .ci/linux-build.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
.ci/linux-build.sh +1 -1
@@ -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
Signature · 1 line
2.51.0
PATCH v2 1/1 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.
---
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(-)
.ci/linux-build.sh +1 -1
@@ -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
Signature · 1 line
2.51.0
Quoted 41 lines
-----Original Message-----
From: Bruce Richardson <[email protected]>
Sent: Monday 19 January 2026 11:56
To: [email protected]
Cc: Bruce Richardson <[email protected]>; Aaron Conole <[email protected]>
Subject: [PATCH v2] ci: improve logging of unit tests runsTo 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 <[email protected]>---
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(-).ci/linux-build.sh +1
-2@@ -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 --
Quoted 1 line
2.51.0
(Using both flags in our local CI for long time.)
Quoted 12 lines · 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.
Quoted 5 lines
Signed-off-by Bruce Richardson <[email protected]>---
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).
CC'ing Patrick and the CI list - just in case any of the labs have any special processing when they pull error logs.
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.
Quoted 30 lines · Aaron Conole
Quoted 12 lines · 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.Quoted 5 lines
Signed-off-by Bruce Richardson <[email protected]>---
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 <[email protected]>CC'ing Patrick and the CI list - just in case any of the labs have any special processing when they pull error logs.
David Marchand
AppliedQuoted 13 lines · 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.
Quoted 1 line
Signed-off-by Bruce Richardson <[email protected]>
Thanks, logs are easier to read like this.
Applied.
Signature · 1 line
David Marchand