Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm members

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm members
Date: 2021-06-23 13:21:02
Message-ID: 3f3f3d9d-fccf-318d-5c16-622778b42645@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 6/22/21 5:11 PM, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> On 6/20/21 6:10 PM, Tom Lane wrote:
>>> (3) Since this only works in v14 and up, older branches would
>>> have to fall back to -DCLOBBER_CACHE_ALWAYS. Perhaps we could
>>> improve the buildfarm client script so that buildfarm owners
>>> just configure "clobber_cache_testing => 1" and then the script
>>> would do the right branch-dependent thing.
>> Maybe. Let's see what you come up with.
> Here's a couple of draft-quality patches --- one for initdb, one
> for the buildfarm --- to implement this idea. These are just
> lightly tested; in particular I've not had the patience to run
> full BF cycles to see how much is actually saved.
>
>

Looks OK for the buildfarm patch. I wonder if we just want to run initdb
once with --clobber-cache instead of once per locale?

cheers

andrew

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-06-23 13:27:30 Re: genbki stricter error handling
Previous Message Alvaro Herrera 2021-06-23 13:08:35 Re: pgbench logging broken by time logic changes