| From: | "Jelte Fennema-Nio" <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "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-17 20:15:55 |
| Message-ID: | DIL87Z9EOS8Z.37BG07ZJPYZ8B@jeltef.nl |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
| Attachment | Content-Type | Size |
|---|---|---|
| v6-0001-Address-feedback-on-changed-pg_regress-output.patch | text/x-patch | 8.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2026-05-17 20:46:08 | Re: [PATCH] Fix REPACK decoding worker not cleaned up on FATAL exit |
| Previous Message | Sami Imseih | 2026-05-17 17:37:23 | Re: Improve pg_stat_statements scalability |