From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Daniel Gustafsson <daniel@yesql.se>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Reporting script runtimes in pg_regress
Date: Mon, 11 Feb 2019 09:30:30 -0500
Message-ID: <6418.1549895430@sss.pgh.pa.us> (raw)
In-Reply-To: <6f1657f9-c58c-ba28-0013-d36a6f6fd246@2ndquadrant.com>
References: <16646.1549770618@sss.pgh.pa.us>
<E7790843-B885-492B-8537-CC9FB39D5F97@yesql.se>
<11413.1549835730@sss.pgh.pa.us>
<6f1657f9-c58c-ba28-0013-d36a6f6fd246@2ndquadrant.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, peter.eisentraut@2ndquadrant.com, daniel@yesql.se, pgsql-hackers@lists.postgresql.org
Subject: Re: Reporting script runtimes in pg_regress
In-Reply-To: <6418.1549895430@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox