Horton

Re: TAP output format in pg_regress

Daniel Gustafsson <daniel@yesql.se>

View thread View on postgr.es
From: Daniel Gustafsson <daniel@yesql.se>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: vignesh C <vignesh21@gmail.com>, Nikolay Shaplov <dhyan@nataraj.su>, Andres Freund <andres@anarazel.de>, Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>, Andrew Dunstan <andrew@dunslane.net>, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2023-03-31T11:12:05Z
Lists: pgsql-hackers 
> On 29 Mar 2023, at 22:08, Daniel Gustafsson <daniel@yesql.se> wrote:
> 
>> On 29 Mar 2023, at 21:14, Daniel Gustafsson <daniel@yesql.se> wrote:
> 
>> Ugh, I clearly should've stayed on the couch yesterday.
> 
> Maybe today as well, just as I had sent this I realized there is mention of the
> output format in the docs that I had missed.  The attached changes that as well
> to match the new format.  (The section in question doesn't mention using meson,
> but I have a feeling that's tackled in one of the meson docs threads.)

Pushed to master now with a few tweaks to comments and docs.  Thanks for all
the reviews, I hope the new format will make meson builds easier/better without
compromising the human readable aspect of traditional builds.

--
Daniel Gustafsson

Commits

  1. pg_regress: Emit TAP compliant output

  2. Consider a failed process as a failed test in pg_regress

  3. Avoid reference to nonexistent array element in ExecInitAgg().