Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm members

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Subject: Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm members
Date: 2021-07-01 17:17:42
Message-ID: 702694.1625159862@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 7/1/21 11:01 AM, Tom Lane wrote:
>> I'm inclined to argue that it's okay to sneak the initdb change into
>> v14, on the grounds that it's needed to fully exploit the change
>> from CLOBBER_CACHE_ALWAYS to debug_invalidate_system_caches_always.
>> Without it, there is no way to do CCA testing on the bootstrap process
>> except by reverting to the old hard-wired way of doing things.
>>
>> Having pushed that, we could try out the buildfarm side of the
>> change and verify it's okay.

> Seems reasonable. I don't have a CCA animal any more, but I guess I
> could set up a test.

I can run a test here --- I'll commandeer sifaka for awhile,
since that's the fastest animal I have.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2021-07-01 17:24:22 Re: Remove unused code from the KnownAssignedTransactionIdes submodule
Previous Message Andrew Dunstan 2021-07-01 17:03:00 Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm members