Re: test/modules/test_oat_hooks vs. debug_discard_caches=1

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@lists.postgresql.org, Tomas Vondra <tomas.vondra@enterprisedb.com>
Date: 2022-11-19T03:10:11Z
Lists: pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> On 2022-11-18 15:55:34 -0500, Tom Lane wrote:
>> We realized today [1] that it's been some time since the buildfarm
>> had any debug_discard_caches (nee CLOBBER_CACHE_ALWAYS) coverage.

> Do we know when it was covered last? I assume it's before the addition of
> test_oat_hooks in 90efa2f5565?

As far as that goes: some digging in the buildfarm DB says that avocet
last did a CCA run on 2021-10-22 and trilobite on 2021-10-24.  They
were then offline completely until 2022-02-10, and when they restarted
the runtimes were way too short to be CCA tests.

Seems like maybe we need a little more redundancy in this bunch of
buildfarm animals.

			regards, tom lane



Commits

  1. Disable debug_discard_caches in test_oat_hooks test.