From 1c9ec13e23004e696735dcbe9c01136bdb86da15 Mon Sep 17 00:00:00 2001 From: Jelte Fennema-Nio Date: Sun, 16 Aug 2026 11:24:57 +0200 Subject: [PATCH v2 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 500 in CI so you can usually see the 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, the multiline diff of a failed comparison, captured output, and the end of the servers' logs. That makes it much easier to find the cause of the failure, but it easily goes over the 100 line default. --- .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 e8eb49b5f15..94e8e755f1d 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=500 --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.55.0