| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, 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-07-05 01:56:24 |
| Message-ID: | 1803389.1656986184@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> I think with a bit of care the tap output could be nearly the same
> "quality". It might not be the absolute "purest" tap output, but who cares.
+1
> For non-parallel tests I think we currently print the test name before running
> the test, which obviously doesn't work well when needing to print the 'ok'
> 'not ok' first.
Is this still a consideration? We got rid of serial_schedule some
time ago.
> I wonder if for parallel tests we should print the test number based on the
> start of the test rather than the finish time?
I think we need the test number to be stable, so it had better be the
ordering appearing in the schedule file. But we already print the
results in that order.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2022-07-05 02:18:57 | Re: Bugs in copyfuncs/equalfuncs support for JSON node types |
| Previous Message | Zhihong Yu | 2022-07-05 01:48:48 | Re: Bugs in copyfuncs/equalfuncs support for JSON node types |