Horton

Re: meson: Make test output much more useful on failure (both in CI and locally)

Jelte Fennema-Nio <postgres@jeltef.nl>

View thread
From: "Jelte Fennema-Nio" <postgres@jeltef.nl>
To: "Andrew Dunstan" <andrew@dunslane.net>, "Peter Eisentraut" <peter@eisentraut.org>, "Corey Huinker" <corey.huinker@gmail.com>
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>
Date: 2026-05-17T20:15:55Z
Lists: pgsql-hackers

Attachments

On Thu Apr 9, 2026 at 11:21 AM CEST, Andrew Dunstan wrote:
> How about something like this, which would only trigger the behaviour if 
> an environment variable is set. Also adds that env setting to 
> cirrus.tasks.yml.

That approach has the problem that then we don't see the diffs anymore
when pg_regress is called from TAP tests. Attached is a patch that I
think addresses the problems with the original version.

P.S. For PG20 I intend to submit a patchset that improves the output of
pg_regress in case of backend crashes. I have a bunch of ideas, but most
of them require some changes to psql and libpq too.