From 55eaeb12ed88d811520cf52cff0c580be10ddaa9 Mon Sep 17 00:00:00 2001 From: Jelte Fennema-Nio Date: Sun, 16 Aug 2026 11:24:57 +0200 Subject: [PATCH v1 01/12] ci: show more than 100 lines of a failing test's log `meson test --print-errorlogs` by default only prints 100 lines of a failing test's log. This increases that to 10000 in CI so you can see the full reason for the failure in the CI output instead of having to download the full logs. This matters more for the pytest tests that later commits add: where a failing TAP test reports little beyond the assertion that failed, pytest reports the failing expression with the values that went into it, the traceback, and whatever the test captured along the way. That makes it much easier to find the cause of the failure, but it also goes over this 100 line default limit. --- .github/workflows/pg-ci.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/pg-ci.yml b/.github/workflows/pg-ci.yml index a2629c8335a..c0dc5ba0360 100644 --- a/.github/workflows/pg-ci.yml +++ b/.github/workflows/pg-ci.yml @@ -59,7 +59,7 @@ env: # Build test dependencies as part of the build step, to see compiler # errors/warnings in one place. MBUILD_TARGET: all testprep - MTEST_ARGS: --print-errorlogs --no-rebuild -C build + MTEST_ARGS: --print-errorlogs --max-lines=10000 --no-rebuild -C build # Can be set to a non-empty value to run a limited set of tests # (e.g. --suite regress to only run the main regression tests). -- 2.54.0