Re: TAP output format in pg_regress
Daniel Gustafsson <daniel@yesql.se>
From: Daniel Gustafsson <daniel@yesql.se>
To: Andres Freund <andres@anarazel.de>
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2022-03-24T12:44:51Z
Lists: pgsql-hackers
Attachments
- v4-0002-Reduce-noise-in-pg_regress-default-output.patch (application/octet-stream) patch v4-0002
- v4-0001-pg_regress-TAP-output-format.patch (application/octet-stream) patch v4-0001
> On 22 Mar 2022, at 00:49, Andres Freund <andres@anarazel.de> wrote: > This is failing with segmentation faults on cfbot: > https://cirrus-ci.com/task/4879227009892352?logs=test_world#L21 > > Looks like something around isolationtester is broken? It could be triggered by plpgsql tests as well, and was (as usual) a silly mistake easily fixed when found. The attached survices repeated check-world for me. > Seems like we might not have energy to push this forward in the next two > weeks, so maybe the CF entry should be marked returned or moved for now? Since there is little use for this without the Meson branch, it should target the same version as that patch. I'll move the patch to the next CF for now. As we discussed off-list I extended this patchset with an attempt to minimize noise as per 20220221164736.rq3ornzjdkmwk2wo@alap3.anarazel.de, but it's not yet done. The attached has a rough draft of adding a --verbose option which gives the current output (and potentially more for debugging), but which by default is off producing minimal noise. -- 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