Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8; format=Flowed
Date: Mon, 18 May 2026 17:26:05 +0200
Message-Id: <DILWOM7ARTNF.1GR02CZT6CTT5@jeltef.nl>
From: "Jelte Fennema-Nio" <postgres@jeltef.nl>
Cc: "Zsolt Parragi" <zsolt.parragi@percona.com>, "Nazir Bilal Yavuz"
 <byavuz81@gmail.com>, "Andres Freund" <andres@anarazel.de>, "PostgreSQL
 Hackers" <pgsql-hackers@lists.postgresql.org>
Subject: Re: meson: Make test output much more useful on failure (both in CI
 and locally)
To: "Alexander Lakhin" <exclusion@gmail.com>, "Peter Eisentraut"
 <peter@eisentraut.org>, "Andrew Dunstan" <andrew@dunslane.net>, "Corey
 Huinker" <corey.huinker@gmail.com>
References: <DFYFWM053WHS.10K8ZPJ605UFK@jeltef.nl>
 <luhx26gz3tiqkndldbobukt4zeaeu2ppd5qgsibf6hknhq6d7e@kngeuarhk5dg>
 <DFZGDORXS9MU.242AFAEFZ6H76@jeltef.nl>
 <CAN55FZ3w-3z=js-3We78P41heKCY1aOMsUz3p7UrQa7amGWL7g@mail.gmail.com>
 <DG7QVVT1F524.2IYU4ICX4GS34@jeltef.nl>
 <CAN4CZFMOBeKh51LqxjMGSSYHWTGPXAE33e+ZWnGgFKm21LJpfw@mail.gmail.com>
 <DH4ZF4BENK7C.IXW5BEFGMFHQ@jeltef.nl>
 <CADkLM=dr-e_k7sh5PL36Hn7G5z6Xno1XHCwAQurv5UWSaUq4-g@mail.gmail.com>
 <DH7GNPMENGF5.3HICJRPB9KQWO@jeltef.nl>
 <CADkLM=d51SaMF+w+k33EhGAFOeP0VQdUZS1mE__dJKkanm2jkw@mail.gmail.com>
 <83961e31-18f6-4a2f-983a-942e3335ba0a@dunslane.net>
 <96944093-b890-4a03-8f03-aa043d1e2ec9@eisentraut.org>
 <3b239431-a945-4e2b-903d-22c7addc528e@gmail.com>
In-Reply-To: <3b239431-a945-4e2b-903d-22c7addc528e@gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/DILWOM7ARTNF.1GR02CZT6CTT5%40jeltef.nl>
Precedence: bulk

On Fri Apr 24, 2026 at 7:00 PM CEST, Alexander Lakhin wrote:
> I've noticed another disadvantage of this log processing: [1] shows the
> misc_functions test's failure, but we can't see timing of the test anymor=
e:
> # ok 27=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 + line=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 6713 ms
> # ... 210 lines omitted ...
> # ok 223=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 + reloptions=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 18169 ms
>
> Previously, a test report for the same failure contained:
> ok 139=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 + merge=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 19699 ms
> not ok 140=C2=A0=C2=A0 + misc_functions=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 18003 ms
> ok 141=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 + sysviews=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 7925 ms

I didn't address this in my v6 (yet). Primarily because this isn't
related to the pg_regress changes, but rather to my change that started
using command_ok in these tests to run pg_regress. I'm thinking a bit if
we can make this nicer, one way would be to have command_ok take an
optional argument that allows disabling truncation in places where we
know the output won't be huge.