Re: meson: Make test output much more useful on failure (both in CI and locally) - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: meson: Make test output much more useful on failure (both in CI and locally)
Date
Msg-id f6531930-4e08-44b8-b710-c19ddbe97fcb@dunslane.net
Whole thread
In response to meson: Make test output much more useful on failure (both in CI and locally)  ("Jelte Fennema-Nio" <postgres@jeltef.nl>)
Responses Re: meson: Make test output much more useful on failure (both in CI and locally)
List pgsql-hackers
On 2026-05-17 Su 4:15 PM, Jelte Fennema-Nio wrote:
> 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.


Why can't the TAP sets set it?


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Sehrope Sarkuni
Date:
Subject: Tighten SCRAM iteration parsing and bound libpq PBKDF2 work
Next
From: Peter Smith
Date:
Subject: Re: Proposal: Conflict log history table for Logical Replication