Re: TAP output format in pg_regress

Daniel Gustafsson <daniel@yesql.se>

From: Daniel Gustafsson <daniel@yesql.se>

To: Andrew Dunstan <andrew@dunslane.net>

Cc: Andres Freund <andres@anarazel.de>, Tom Lane <tgl@sss.pgh.pa.us>, Peter Eisentraut <peter.eisentraut@enterprisedb.com>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>

Date: 2022-09-01T12:21:18Z

Lists: pgsql-hackers

Attachments

v8-0001-Make-pg_regress-output-format-TAP-compliant.patch (application/octet-stream) patch v8-0001

> On 18 Aug 2022, at 16:40, Andrew Dunstan <andrew@dunslane.net> wrote:
> 
> On 2022-08-18 Th 07:24, Daniel Gustafsson wrote:
>> 
>> One thing I haven't researched yet is if the Buildfarm or CFBot parses the
>> current output in any way or just check the exit status of the testrun.
> 
> Buildfarm: just the status.

Thanks for confirming, the same is true for CFBot AFAICT.

Attached is a v8 which fixes a compiler warning detected by the CFBot.

--
Daniel Gustafsson		https://vmware.com/

Commits

pg_regress: Emit TAP compliant output
- 558fff0adfa0 16.0 landed
Consider a failed process as a failed test in pg_regress
- 337903a16fb0 16.0 landed
Avoid reference to nonexistent array element in ExecInitAgg().
- 92957ed98c5c 16.0 cited