Re: Subscription tests fail under CLOBBER_CACHE_ALWAYS

Tomas Vondra <tomas.vondra@enterprisedb.com>

From: Tomas Vondra <tomas.vondra@enterprisedb.com>
To: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@lists.postgresql.org
Date: 2021-05-19T12:54:09Z
Lists: pgsql-hackers
On 5/19/21 1:42 AM, Tom Lane wrote:
> I discovered $SUBJECT after wondering why hyrax hadn't reported
> in recently, and trying to run check-world under CCA to see if
> anything got stuck.  Indeed it did --- although this doesn't
> explain the radio silence from hyrax, because that animal doesn't
> run any TAP tests.  (Neither does avocet, which I think is the
> only other active CCA critter.  So this could have been broken
> for a very long time.)
> 

There are three CCA animals on the same box (avocet, husky and 
trilobite) with different compilers, running in a round-robin manner. 
One cycle took about 14 days, but about a month ago the machine got 
stuck, requiring a hard reboot about a week ago (no idea why it got 
stuck). It has more CPU power now (8 cores instead of 2), so it should 
take less time to run one test cycle.

avocet already ran all the tests, husky is running HEAD at the moment 
and then it'll be trilobite's turn ... AFAICS none of those runs seems 
to have failed or got stuck so far.

regards

-- 
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



Commits

  1. Be more verbose when the postmaster unexpectedly quits.

  2. Fix access to no-longer-open relcache entry in logical-rep worker.