Horton

Re: Reporting script runtimes in pg_regress

John Naylor <john.naylor@2ndquadrant.com>

View thread View on postgr.es
From: John Naylor <john.naylor@2ndquadrant.com>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Daniel Gustafsson <daniel@yesql.se>, pgsql-hackers@lists.postgresql.org
Date: 2019-02-15T16:03:13Z
Lists: pgsql-hackers 
On 2/15/19, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote:
> We should also strive to align "FAILED" properly.  This is currently
> quite unreadable:
>
>      int4                         ... ok (128 ms)
>      int8                         ... FAILED (153 ms)
>      oid                          ... ok (163 ms)
>      float4                       ... ok (231 ms)

If I may play devil's advocate, who cares how long it takes a test to
fail? If it's not difficult, leaving the time out for failures would
make them stand out more.

-- 
John Naylor                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Commits

  1. Align timestamps in pg_regress output

  2. De-clutter display of script runtimes in pg_regress.

  3. Add per-test-script runtime display to pg_regress.