Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm members

Andrew Dunstan <andrew@dunslane.net>

From: Andrew Dunstan <andrew@dunslane.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2021-06-23T13:21:02Z
Lists: pgsql-hackers
On 6/22/21 5:11 PM, Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.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




Commits

  1. Add --clobber-cache option to initdb, for CCA testing.