ci: pass --no-stdsplit to meson test

Hopefully, we will get more informative logs on failure.
This commit is contained in:
Yu Watanabe
2025-12-07 09:09:03 +09:00
parent 450f4ed58a
commit a5d0e0ebb2
2 changed files with 3 additions and 3 deletions
+1 -1
View File
@@ -47,7 +47,7 @@ for phase in "${PHASES[@]}"; do
# correctly detect the environment.
env \
SYSTEMD_IN_CHROOT=yes \
meson test -C build --print-errorlogs
meson test -C build --print-errorlogs --no-stdsplit
;;
CLEANUP)
info "Cleanup phase"
+2 -2
View File
@@ -109,7 +109,7 @@ for phase in "${PHASES[@]}"; do
run_meson -Dnobody-group=nogroup --werror -Dtests=unsafe -Dslow-tests=true -Dfuzz-tests=true "${MESON_ARGS[@]}" build
ninja -C build -v
# Ensure setting a timezone (like the reproducible build tests do) does not break time/date unit tests
TZ=GMT+12 meson test "${MESON_TEST_ARGS[@]}" -C build --print-errorlogs
TZ=GMT+12 meson test "${MESON_TEST_ARGS[@]}" -C build --print-errorlogs --no-stdsplit
;;
RUN_ASAN_UBSAN|RUN_GCC_ASAN_UBSAN|RUN_CLANG_ASAN_UBSAN|RUN_CLANG_ASAN_UBSAN_NO_DEPS)
# TODO: drop after we switch to ubuntu 26.04
@@ -151,7 +151,7 @@ for phase in "${PHASES[@]}"; do
# during debugging, wonderful), so let's at least keep a workaround
# here to make the builds stable for the time being.
(set +x; while :; do echo -ne "\n[WATCHDOG] $(date)\n"; sleep 30; done) &
meson test --timeout-multiplier=3 -C build --print-errorlogs
meson test --timeout-multiplier=3 -C build --print-errorlogs --no-stdsplit
;;
CLEANUP)
info "Cleanup phase"