From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
Subject: | Re: test/modules/test_oat_hooks vs. debug_discard_caches=1 |
Date: | 2022-11-19 03:10:11 |
Message-ID: | 2316565.1668827411@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2022-11-19 03:12:24 | More efficient build farm animal wakeup? |
Previous Message | Peter Geoghegan | 2022-11-19 01:06:57 | Re: New strategies for freezing, advancing relfrozenxid early |