| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: TAP output format in pg_regress |
| Date: | 2022-07-04 22:06:31 |
| Message-ID: | 1640889.1656972391@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:
>> Both of those things are fairly critical for test development. You
>> need to know what else might be running in parallel with a test case,
>> and you need to know whether you just bloated the runtime unreasonably.
> That should be doable with tap as well - afaics the output of that could
> nearly be the same as now, preceded by a #.
I don't mind minor changes like prefixing # --- I just don't want
to lose information.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Roberto C. Sánchez | 2022-07-04 22:06:51 | Re: Request for assistance to backport CVE-2022-1552 fixes to 9.6 and 9.4 |
| Previous Message | Daniel Gustafsson | 2022-07-04 22:06:04 | Re: TAP output format in pg_regress |