Re: TAP output format in pg_regress

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: TAP output format in pg_regress
Date: 2022-09-01 12:21:18
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

> On 18 Aug 2022, at 16:40, Andrew Dunstan <andrew(at)dunslane(dot)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

Attachment Content-Type Size
v8-0001-Make-pg_regress-output-format-TAP-compliant.patch application/octet-stream 32.3 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Guo 2022-09-01 12:24:32 Re: [POC] Allow flattening of subquery with a link to upper query
Previous Message Matthias van de Meent 2022-09-01 12:18:42 Re: Tracking last scan time