From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: TAP output format in pg_regress |
Date: | 2022-07-04 19:33:36 |
Message-ID: | f197e2c4-9ab9-5aaa-0a69-7b60b60cd969@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 04.07.22 16:39, Tom Lane wrote:
> Probably is, because this is bad:
>
>> ... The proposed default format now hides the
>> fact that some tests are started in parallel. I remember the last time
>> I wanted to tweak the output of the parallel tests, people were very
>> attached to the particular timing and spacing of the current output. So
>> I'm not sure people will like this.
> and so is this:
>
>> The timing output is very popular. Where is that in the TAP output?
> 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.
I don't think there is a reason these couldn't be shown in TAP output as
well.
Even if we keep the two output formats in parallel, it would be good if
they showed the same set of information.
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2022-07-04 19:38:42 | Re: doc: BRIN indexes and autosummarize |
Previous Message | Peter Eisentraut | 2022-07-04 18:37:30 | Re: Temporary file access API |