Horton
Menu

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

Alexander Lakhin <exclusion@gmail.com>

View thread
From: Alexander Lakhin <exclusion@gmail.com>
To: Peter Eisentraut <peter@eisentraut.org>, Andrew Dunstan <andrew@dunslane.net>, Corey Huinker <corey.huinker@gmail.com>, 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>
Date: 2026-04-24T17:00:00Z
Lists: pgsql-hackers 
Hello hackers,

07.04.2026 16:15, Peter Eisentraut wrote:
> On 02.04.26 14:25, Andrew Dunstan wrote:
>> Committed with minor tidy up. The main change was to add a @CARP_NOT setting in Utils.pm, so that croak() would look 
>> back past Cluster.pm to the TAP script caller.
>
> I would like to register a vote against this new behavior:

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 anymore:
# ok 27        + line                                     6713 ms
# ... 210 lines omitted ...
# ok 223       + reloptions                              18169 ms

Previously, a test report for the same failure contained:
ok 139       + merge                                   19699 ms
not ok 140   + misc_functions                          18003 ms
ok 141       + sysviews                                 7925 ms

[1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2026-04-24%2001%3A26%3A26

Best regards,10
Alexander

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Use command_ok for pg_regress calls in 002_pg_upgrade and 027_stream_regress

  2. perl tap: Show die reason in TAP output

  3. perl tap: Show failed command output

  4. perl tap: Use croak instead of die in our helper modules

  5. pg_regress: Include diffs in TAP output