Re: Reporting script runtimes in pg_regress

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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 14:13:48
Message-ID: 422e0383-79e1-7c10-5771-1e232e3349ca@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019-02-15 14:32, Peter Eisentraut wrote:
> identity ... ok 238 ms
> partition_join ... ok 429 ms
> partition_prune ... ok 786 ms
> reloptions ... ok 94 ms
> hash_part ... ok 78 ms
> indexing ... ok 1298 ms
> partition_aggregate ... ok 727 ms
> partition_info ... ok 110 ms
> test event_trigger ... ok 128 ms
> test fast_default ... ok 173 ms
> test stats ... ok 637 ms

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)

--
Peter Eisentraut http://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 Peter Eisentraut 2019-02-15 14:16:00 Re: [HACKERS] Time to change pg_regress diffs to unified by default?
Previous Message Konstantin Knizhnik 2019-02-15 14:03:24 Re: libpq compression