Horton
Menu

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

Corey Huinker <corey.huinker@gmail.com>

View thread
From: Corey Huinker <corey.huinker@gmail.com>
To: 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>, andrew@dunslane.net
Date: 2026-03-20T18:13:13Z
Lists: pgsql-hackers 
>
> Shortened it using your example run.
>

Glad I was able to help.


> > 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.
>

I've held off on doing that in my proposed commits so as not to be
presumptuous, but I can see where having it available would be a
convenience for the committer. This will be a good test of that.

Applies clean to master, passes tests. Ship it.

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