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

From Tom Lane
Subject Re: Reporting script runtimes in pg_regress
Date
Msg-id 6418.1549895430@sss.pgh.pa.us
Whole thread Raw
In response to Re: Reporting script runtimes in pg_regress  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Reporting script runtimes in pg_regress  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Re: Reporting script runtimes in pg_regress  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
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?

            regards, tom lane


pgsql-hackers by date:

Previous
From: Evgeniy Efimkin
Date:
Subject: Re: [WIP] CREATE SUBSCRIPTION with FOR TABLES clause (table filter)
Next
From: Dmitry Vasiliev
Date:
Subject: Logical replication and restore from pg_basebackup