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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: Running tests under valgrind is getting slower at an alarming pace
Date: 2021-10-08 19:41:09
Message-ID: fa6f787e-6151-c4a6-ed13-02a311225609@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 10/6/21 10:03 PM, Andres Freund wrote:
> Hi,
>
> On 2021-10-06 09:47:54 -0700, Andres Freund wrote:
>> I'll also try to figure out print a bit more detail about timing for each tap
>> test, looks like I need to figure out how to pass PROVE_TEST='--timer' through
>> the buildfarm. Shouldn't be too hard.
> Turns out that the buildfarm already adds --timer. I added -j4 to allow for
> some concurrency in tap tests, but unfortunately my animals fell over after
> that (thanks Michael for noticing).
>
> Looks like the buildfarm client code isn't careful enough quoting PROVE_FLAGS?
>
> my $pflags = "PROVE_FLAGS=--timer";
> if (exists $ENV{PROVE_FLAGS})
> {
> $pflags =
> $ENV{PROVE_FLAGS}
> ? "PROVE_FLAGS=$ENV{PROVE_FLAGS}"
> : "";
> }
>
> @makeout =
> run_log("cd $dir && $make NO_LOCALE=1 $pflags $instflags $taptarget");
>
> Which doesn't work if pflags ends up as '-j4 --timer' or such...

see
<https://github.com/PGBuildFarm/client-code/commit/85ba5866c334f16c8683b524743f4d714be28d77>

cheers

andrew

--

Andrew Dunstan
EDB: https://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bossart, Nathan 2021-10-08 20:48:58 Re: Pre-allocating WAL files
Previous Message Thomas Munro 2021-10-08 19:40:26 Re: Time to upgrade buildfarm coverage for some EOL'd OSes?