Re: Reporting script runtimes in pg_regress - Mailing list pgsql-hackers

From Amit Langote
Subject Re: Reporting script runtimes in pg_regress
Date
Msg-id 3e781ef4-04cb-5670-ee2b-7c0e99f72ece@lab.ntt.co.jp
Whole thread Raw
In response to Re: Reporting script runtimes in pg_regress  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Reporting script runtimes in pg_regress
List pgsql-hackers
On 2019/02/11 23:30, Tom Lane wrote:
> Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
>> Now that I see this in action, it makes the actual test results harder
>> to identify flying by.  I understand the desire to collect this timing
>> data, but that is a special use case and not relevant to the normal use
>> of the test suite, which is to see whether the test passes.  Can we make
>> this optional please?
> 
> Well, I want the buildfarm to produce this info, so it's hard to see
> how to get that without the timings being included by default.  I take
> your point that it makes the display look a bit cluttered, though.
> Would it help to put more whitespace between the status and the timing?

+1.  Maybe, not as much whitespace as we get today between the test name
and "... ok", but at least more than just a single space.

Thanks,
Amit



pgsql-hackers by date:

Previous
From: Chapman Flack
Date:
Subject: Re: BUG #15629: Typo in Documentation
Next
From: Michael Paquier
Date:
Subject: Re: Connection slots reserved for replication