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

Jelte Fennema <postgres@jeltef.nl>

From: "Jelte Fennema-Nio" <postgres@jeltef.nl>
To: "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>, <andrew@dunslane.net>
Date: 2026-03-20T08:19:19Z
Lists: pgsql-hackers

Attachments

On Thu Mar 19, 2026 at 8:44 PM CET, Corey Huinker wrote:
>>
>>
>> Finally I added a new commit which starts to use command_ok in
>> 002_pg_upgrade.pl and 027_stream_regress.pl to get the new nicer output.
>>
>
> I tried this out, and am very pleased with the results.

Thanks for the review.

> nitpick: comment sentence needs a closing '.'

Fixed

> v4-0005: the commit message is probably too bulky to be used as-is, but the
> committer was going to change that anyway and right now too much
> information is way better than not enough.

Shortened it using your example run.

> I can't wait to use this.

Me too :) I've also added the Author/Reviewed-By/Discussion footers to
the commits to make the committers job easier.

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