Re: TAP output format in pg_regress

Daniel Gustafsson <daniel@yesql.se>

From: Daniel Gustafsson <daniel@yesql.se>

To: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>, Andres Freund <andres@anarazel.de>

Date: 2022-02-22T14:10:11Z

Lists: pgsql-hackers

Attachments

v3-0001-pg_regress-TAP-output-format.patch (application/octet-stream) patch v3-0001

> On 22 Feb 2022, at 00:08, Daniel Gustafsson <daniel@yesql.se> wrote:

> I'll fix that.

The attached v3 fixes that thinko, and cleans up a lot of the output which
isn't diagnostic per the TAP spec to make it less noisy.  It also fixes tag
support used in the ECPG tests and a few small cleanups.  There is a blank line
printed which needs to be fixed, but I'm running out of time and wanted to get
a non-broken version on the list before putting it aside for today.

The errorpaths that exit(2) the testrun should be converted to "bail out" lines
when running with TAP output, but apart from that I think it's fairly spec
compliant.

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