Re: TAP output format in pg_regress
Daniel Gustafsson <daniel@yesql.se>
From: Daniel Gustafsson <daniel@yesql.se>
To: Nikolay Shaplov <dhyan@nataraj.su>
Cc: 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>, Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Date: 2022-11-28T19:27:02Z
Lists: pgsql-hackers
Attachments
- v14-0001-Change-pg_regress-output-format-to-be-TAP-compli.patch (application/octet-stream) patch v14-0001
> On 28 Nov 2022, at 20:02, Nikolay Shaplov <dhyan@nataraj.su> wrote: > From my reviewer's point of view patch is ready for commit. > > Thank you for your patience :-) Thanks for review. The attached tweaks a few comments and attempts to address the compiler warning error in the CFBot CI. Not sure I entirely agree with the compiler there but here is an attempt to work around it at least (by always copying the va_list for the logfile). It also adds a missing va_end for the logfile va_list. I hope this is close to a final version of this patch (commitmessage needs a bit of work though). > PS Should I change commitfest status? Sure, go ahead. -- 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