[PATCH] ci: improve logging of unit tests runs

[Bruce Richardson <bruce.richardson@intel.com>]

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