Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lTakr-00063O-4L for pgsql-committers@arkaria.postgresql.org; Tue, 06 Apr 2021 01:43:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lTakp-0003En-PJ for pgsql-committers@arkaria.postgresql.org; Tue, 06 Apr 2021 01:43:43 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lTakp-0003Eg-KI for pgsql-committers@lists.postgresql.org; Tue, 06 Apr 2021 01:43:43 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lTakm-0001mV-PN for pgsql-committers@lists.postgresql.org; Tue, 06 Apr 2021 01:43:42 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 1361hcUb939271; Mon, 5 Apr 2021 21:43:39 -0400 From: Tom Lane To: Michael Paquier cc: pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Refactor all TAP test suites doing connection checks In-reply-to: <936576.1617669613@sss.pgh.pa.us> References: <513200.1617634642@sss.pgh.pa.us> <932059.1617663467@sss.pgh.pa.us> <933130.1617665023@sss.pgh.pa.us> <935457.1617668131@sss.pgh.pa.us> <936576.1617669613@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Mon, 05 Apr 2021 20:40:13 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <939269.1617673418.1@sss.pgh.pa.us> Date: Mon, 05 Apr 2021 21:43:38 -0400 Message-ID: <939270.1617673418@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk I wrote: > Well, since it's a race condition it's obviously going to be sensitive to > machine speed. I think that Perl version, or more likely version of > IPC::Run or a related module, may enter into it too. prairiedog has > gotten through the tests several times since yesterday without failing, > yet it's significantly slower than the other PPC Mac I was able to > consistently reproduce the problem on. I don't think those two have > the same vintage of Perl installation, though, so Perl version seems > like a likely explanation. Just for the archives' sake: prairiedog (passed 3 out of 3 tries): 450MHz PPC32 Perl 5.8.3 $ perl -MIPC::Run -e 'print $IPC::Run::VERSION ."\n";' 0.79 (file dates on the IPC::Run files are 2004) gaur (failed 1 out of 1 tries): 360MHz HPPA Perl 5.8.9 IPC::Run 0.94 (file dates 2014) my other PPC Mac (failed consistently, 10 out of 10): 1.33GHz PPC32 Perl 5.8.8 IPC::Run 20180523.0 Not sure what to make of that, though a regression in IPC::Run seems possible. It's also possible that buildfarm script (the first two) versus manual invocation (the last) is related somehow. regards, tom lane