From: Tom Lane <tgl@sss.pgh.pa.us>
To: Noah Misch <noah@leadboat.com>
cc: Andres Freund <andres@anarazel.de>, Peter Geoghegan <pg@bowt.ie>,
        David Rowley <dgrowleyml@gmail.com>,
        PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Intermittent buildfarm failures on wrasse
In-reply-to: <20220415025019.GA863781@rfd.leadboat.com>
References: <20220414161850.ibqkevxcv6a7vdxg@alap3.anarazel.de>
 <1521388.1649953580@sss.pgh.pa.us> <1547912.1649971995@sss.pgh.pa.us>
 <CAH2-Wz=DHY2LV7=2aVd=qz6AbQhFK7KJRNL5ZwgB7dyno_gzdg@mail.gmail.com>
 <1553951.1649975018@sss.pgh.pa.us>
 <CAH2-WzngTjUk_65ESmrMf40WTqasrmWG0gpwnvcN+mXsoXT7qQ@mail.gmail.com>
 <CAH2-WznXXkkfE_y9ieaHkEQj31HeMAqJBtJPmDY+EpyVg1QywQ@mail.gmail.com>
 <1570894.1649986347@sss.pgh.pa.us>
 <20220415015249.kfsqxujrf2bn2wz6@alap3.anarazel.de>
 <20220415024515.GA862547@rfd.leadboat.com>
 <20220415025019.GA863781@rfd.leadboat.com>
Comments: In-reply-to Noah Misch <noah@leadboat.com>
	message dated "Thu, 14 Apr 2022 19:50:19 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1579177.1649991964.1@sss.pgh.pa.us>
Date: Thu, 14 Apr 2022 23:06:04 -0400
Message-ID: <1579178.1649991964@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1579178.1649991964%40sss.pgh.pa.us>
Precedence: bulk

Noah Misch <noah@leadboat.com> writes:
> But 24s after that email, it did reproduce the problem.

Ain't that always the way.

> Same symptoms as the
> last buildfarm runs, including visfrac=0.  I'm attaching my script.  (It has
> various references to my home directory, so it's not self-contained.)

That's interesting, because I see you used installcheck-parallel,
which I'd not been using on the grounds that wrasse isn't parallelizing
these runs.  That puts a big hole in my working assumption that the
problem is one of timing.  I'm now suspecting that the key issue is
something about how wrasse is building the executables that I did
not exactly reproduce.  I did not try to copy the build details
involving stuff under your home directory (like the private openldap
version), mainly because it didn't seem like openldap or uuid or
perl could be involved at all.  But maybe somehow?

			regards, tom lane