Re: Reporting script runtimes in pg_regress

From: John Naylor <john(dot)naylor(at)2ndquadrant(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Daniel Gustafsson <daniel(at)yesql(dot)se>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Reporting script runtimes in pg_regress
Date: 2019-02-15 16:03:13
Message-ID: CACPNZCuN6c6fvjX8C61F+ZhLWjbqF3L3OSBEgCKZAzkTiz8erg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2/15/19, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2019-02-15 16:04:12 Re: Using POPCNT and other advanced bit manipulation instructions
Previous Message Tomas Vondra 2019-02-15 15:58:40 Re: Protect syscache from bloating with negative cache entries