From: Tom Lane <tgl@sss.pgh.pa.us>
To: Heikki Linnakangas <hlinnaka@iki.fi>
cc: pgsql-hackers <pgsql-hackers@postgresql.org>,
        Thomas Munro <thomas.munro@gmail.com>
Subject: Re: Weird test mixup
In-reply-to: <2387221.1710454778@sss.pgh.pa.us>
References: <10fd6cdd-c5d9-46fe-9fa1-7e661191309e@iki.fi>
 <2387221.1710454778@sss.pgh.pa.us>
Comments: In-reply-to Tom Lane <tgl@sss.pgh.pa.us>
	message dated "Thu, 14 Mar 2024 18:19:38 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2388883.1710455439.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 14 Mar 2024 18:30:39 -0400
Message-ID: <2388884.1710455439@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2388884.1710455439%40sss.pgh.pa.us>
Precedence: bulk

I wrote:
> Heikki Linnakangas <hlinnaka@iki.fi> writes:
>> Somehow the 'gin-leave-leaf-split-incomplete' injection point was activ=
e =

>> in the 'intarray' test. That makes no sense. That injection point is =

>> only used by the test in src/test/modules/gin/. Perhaps that ran at the=
 =

>> same time as the intarray test? But they run in separate instances, wit=
h =

>> different data directories.

> Do they?  It'd be fairly easy to explain this if these things were
> being run in "installcheck" style.  I'm not sure about CI, but from
> memory, the buildfarm does use installcheck for some things.

Hmm, Munro's comment yesterday[1] says that current CI does use
installcheck mode in some cases.

			regards, tom lane

[1] https://www.postgresql.org/message-id/CA+hUKGJYhcG_o2nwSK6r01eOZJwNWUJ=
UbX=3D=3DAVnW84f-+8yamQ@mail.gmail.com