Postgres Pro
Downloads
Home   >   mailing lists

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

From John Naylor
Subject Re: Reporting script runtimes in pg_regress
Date
Msg-id CACPNZCuN6c6fvjX8C61F+ZhLWjbqF3L3OSBEgCKZAzkTiz8erg@mail.gmail.com
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  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
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

pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Protect syscache from bloating with negative cache entries
Next
From: Alvaro Herrera
Date:
Subject: Re: Using POPCNT and other advanced bit manipulation instructions