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>
Subject: Re: test/modules/test_oat_hooks vs. debug_discard_caches=1
Date: Fri, 18 Nov 2022 22:10:11 -0500
Message-ID: <2316565.1668827411@sss.pgh.pa.us> (raw)
In-Reply-To: <20221119003349.uzpopxq2skgrmwc4@awork3.anarazel.de>
References: <2267406.1668804934@sss.pgh.pa.us>
<20221119003349.uzpopxq2skgrmwc4@awork3.anarazel.de>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, tomas.vondra@enterprisedb.com
Subject: Re: test/modules/test_oat_hooks vs. debug_discard_caches=1
In-Reply-To: <2316565.1668827411@sss.pgh.pa.us>
References: <2267406.1668804934@sss.pgh.pa.us> <20221119003349.uzpopxq2skgrmwc4@awork3.anarazel.de> <2316565.1668827411@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox