Re: Running tests under valgrind is getting slower at an alarming pace - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Running tests under valgrind is getting slower at an alarming pace
Date
Msg-id 4148972.1633539514@sss.pgh.pa.us
Whole thread Raw
In response to Re: Running tests under valgrind is getting slower at an alarming pace  (Andres Freund <andres@anarazel.de>)
Responses Re: Running tests under valgrind is getting slower at an alarming pace  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> One thing I think would really help is having the total time for each run
> visible in an animals run history. That way we could pinpoint regressions
> reasonably efficiently, right now that's not easily possible without writing
> nontrivial queries to the buildfarm database...

+1.  I've lost count of how often I've had to drill down to an individual
run just because I wanted to see how long it took.  If we could fit that
into the branch history pages like

https://buildfarm.postgresql.org/cgi-bin/show_history.pl?nm=jay&br=HEAD

it'd be really useful IMO.

Perhaps we could replace "OK" with the total time, so as to avoid making
these tables bigger?  (This presumes that the time for a failed run isn't
so interesting.)

            regards, tom lane



pgsql-hackers by date:

Previous
From: Suraj Khamkar
Date:
Subject: Re: [PATCH] Added TRANSFORM FOR for COMMENT tab completion
Next
From: Bruce Momjian
Date:
Subject: Re: storing an explicit nonce