Re: Reporting script runtimes in pg_regress
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Daniel Gustafsson <daniel@yesql.se>, pgsql-hackers@lists.postgresql.org
Date: 2019-02-11T14:30:30Z
Lists: 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
Commits
-
Align timestamps in pg_regress output
- 148cf5f462e5 12.0 landed
-
De-clutter display of script runtimes in pg_regress.
- 93b5cc039e23 12.0 landed
-
Add per-test-script runtime display to pg_regress.
- 72d71e03563b 12.0 landed