Re: Running tests under valgrind is getting slower at an alarming pace

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Running tests under valgrind is getting slower at an alarming pace
Date: 2021-10-06 16:58:34
Message-ID: 4148972.1633539514@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2021-10-06 17:05:49 Re: storing an explicit nonce
Previous Message Suraj Khamkar 2021-10-06 16:57:32 Re: [PATCH] Added TRANSFORM FOR for COMMENT tab completion