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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
Cc: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: meson: Make test output much more useful on failure (both in CI and locally)
Date: 2026-05-24 22:18:40
Message-ID: f6531930-4e08-44b8-b710-c19ddbe97fcb@dunslane.net
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2026-05-25 01:36:42 Re: Proposal: Conflict log history table for Logical Replication
Previous Message Sehrope Sarkuni 2026-05-24 20:04:07 Tighten SCRAM iteration parsing and bound libpq PBKDF2 work