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 1mB0a6-0006f7-G7 for buildfarm-members@arkaria.postgresql.org; Tue, 03 Aug 2021 20:00:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mB0a5-00046w-Fi for buildfarm-members@arkaria.postgresql.org; Tue, 03 Aug 2021 20:00:05 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mB0a5-00046o-Ac for buildfarm-members@lists.postgresql.org; Tue, 03 Aug 2021 20:00:05 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mB0a3-0007Mp-AP for buildfarm-members@postgresql.org; Tue, 03 Aug 2021 20:00:04 +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 173K00kt1774333; Tue, 3 Aug 2021 16:00:00 -0400 From: Tom Lane To: Andrew Dunstan cc: buildfarm-members@postgresql.org Subject: Re: Release 13 of the PostgreSQL BuildFarm client In-reply-to: <0234f0ff-221a-e6a4-39c7-137ed4edb74e@dunslane.net> References: <18c03f7e-3ab9-f7b4-9248-feb85b0f03ed@dunslane.net> <1660080.1627945870@sss.pgh.pa.us> <5462d8bd-b8aa-3c38-b078-4bf5e94f8eba@dunslane.net> <0234f0ff-221a-e6a4-39c7-137ed4edb74e@dunslane.net> Comments: In-reply-to Andrew Dunstan message dated "Tue, 03 Aug 2021 15:14:41 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1774331.1628020800.1@sss.pgh.pa.us> Date: Tue, 03 Aug 2021 16:00:00 -0400 Message-ID: <1774332.1628020800@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andrew Dunstan writes: > I'm planning on issuing a 12.1 release fairly soon with this patch, but > as I developed it fairly quickly and through the fog of some painkillers > I'd appreciate more eyes on it first :-) I tested this on gaur, and it seems to work --- at least, it gets through the git checkout step now. (It'll be a few hours before the run finishes.) One nit is that personally I could do without this: + my $gversion = `git --version`; + chomp $gversion; + print "$gversion too old to for automatic default branch update\n"; Aside from the message typo, that'll produce useless every-run chatter in affected owners' cron logs. I'd probably soon set skip_git_default_check to silence it, at which point it might as well not be there. Thanks for fixing it, though. I wasted a couple of hours last night trying to build current git on prairiedog and gaur, with no luck so far. I think just blowing away their git repos when the master-branch rename happens will be a much more appropriate amount of effort. regards, tom lane