Re: TAP output format in pg_regress - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: TAP output format in pg_regress
Date
Msg-id f197e2c4-9ab9-5aaa-0a69-7b60b60cd969@enterprisedb.com
Whole thread Raw
In response to Re: TAP output format in pg_regress  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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.



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Temporary file access API
Next
From: Alvaro Herrera
Date:
Subject: Re: doc: BRIN indexes and autosummarize