Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eXAOP-0008V0-3t for buildfarm-members@arkaria.postgresql.org; Thu, 04 Jan 2018 18:37:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eXAOO-0000hv-H8 for buildfarm-members@arkaria.postgresql.org; Thu, 04 Jan 2018 18:37:28 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eXAOO-0000hl-9g for buildfarm-members@lists.postgresql.org; Thu, 04 Jan 2018 18:37:28 +0000 Received: from mail-yw0-x242.google.com ([2607:f8b0:4002:c05::242]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1eXAOH-0007Jr-7L for buildfarm-members@postgresql.org; Thu, 04 Jan 2018 18:37:26 +0000 Received: by mail-yw0-x242.google.com with SMTP id k80so920198ywe.0 for ; Thu, 04 Jan 2018 10:37:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=from:subject:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=fUyMrSvElwUwsmj1SRn6Mu35E5CdrNLLZFlq4Xr2ShE=; b=lvEbH9X+rwsHzjGz2A98FiC+RtbWZcz8SmX2vuLtARB0R0Xrxd1l3Lsd2Y4v/IqYJc 9mWI5SNqGdSdyjwQozf/GEyREYSQCpmkv9+v+ffcmQHFr6NWuUM9LO3O99PFSzerADpc XQOYcJ4K4GTgVQi+QEQjSWjrQVAzpGSzdjZevZliQO3987iLsJBph+qZODlmBkFRC0ME TXYBrm8KZ/A8F7dFpW8hcjMxyNCiMv5kj1s/vuM701+lVlKMtPN1BUWYpKcmj5M05Jw0 cXBkRycFPARJGywa+L/xIA6NIuWCnxKnJdqq+WjovtJb/Yxc0GT6fuTcHuLxAYiyn6te kNWg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=fUyMrSvElwUwsmj1SRn6Mu35E5CdrNLLZFlq4Xr2ShE=; b=W2DMs9SbS7TCu+VLpQUicPD1YQ/OtsISNCOgD4p7j2VHBuvjdzNAyQRplBHd7TrxTc 5NSy7DHqGjtQKACGpBH+1Y0lqFT8ykkL+x53XuOL56Wsb7PHWWMeRLNX09S+fxIuGoi7 5x42GA0NvyOgN9Lw0ay6Mlyy/ia/6kfggK8vEHbPHTvwGsHBrRK5vzxAlfXjUzMZkXr7 wEYaGJCPnoBf3XF5R2CaAE7jPrU5bsd9k7piMG2F2G3Ta0opqX53WYsdWNFhLYUAydme 8w0s0tVQHQlKvXBB3BOPRqzH7cEdS+QuejlgAbhiw/3LNHCAU8s8JdBJHioAAemDiA+y cPnw== X-Gm-Message-State: AKGB3mJqzcvoyiG97e5K/ATljiKhNfrKtuoWqQyoda/63Qv77MCaf6lo +ds77pvVutBkMMbKr5awdrByY22ciVlIPohr58l0q3Vs+CwCX6gaMlvXHFFhfvJwTYqS5dNM8Xu zsP9eai4ZeQwYVDdVoA7CLxSIPdtWHPoCOwxuaXImsQdV5j2LDiGVn1r5eXsw/S9RQd3mb4tEyx 1sHLdW5Gv7CJkW/IWSgg== X-Google-Smtp-Source: ACJfBosz257lgXrezAyfWIOMNbF7A5jxJsMvjni2itATZTPUeXoPHSRBpTMBDrep6/v/aVj+QAd0sQ== X-Received: by 10.129.62.1 with SMTP id l1mr445544ywa.215.1515091039904; Thu, 04 Jan 2018 10:37:19 -0800 (PST) Received: from [192.168.10.146] ([98.122.175.38]) by smtp.gmail.com with ESMTPSA id x66sm1627859ywb.107.2018.01.04.10.37.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Jan 2018 10:37:19 -0800 (PST) From: Andrew Dunstan X-Google-Original-From: Andrew Dunstan Subject: Re: Announcing Release 6 of PostgreSQL Buildfarm client To: Tom Lane Cc: buildfarm-members@postgresql.org References: <59bfeba7-8ee0-31da-9db9-610002f9c841@2ndQuadrant.com> <8725.1515087312@sss.pgh.pa.us> <9420.1515088313@sss.pgh.pa.us> Message-ID: <9053ed57-0efc-e2f3-5bff-6db631b46b0b@2ndQuadrant.com> Date: Thu, 4 Jan 2018 13:37:18 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-MW List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 01/04/2018 01:27 PM, Andrew Dunstan wrote: > > On 01/04/2018 12:51 PM, Tom Lane wrote: >> I wrote: >>> which means I get mail every time the cron script runs. Needless >>> to say, that will not do. Previously, mail only showed up when >>> there was a git checkout failure. How do I get back to the >>> old behavior? >> Diff'ing the v5 and v6 releases soon provided the answer: for some >> reason v6 is forcing the verbose switch on. I hope that was >> unintentional? Anyway, I'm happy again after applying this patch: >> >> --- PGBuild/Options.pm~ 2018-01-04 08:38:29.000000000 -0500 >> +++ PGBuild/Options.pm 2018-01-04 12:40:14.000000000 -0500 >> @@ -78,8 +78,6 @@ >> GetOptions(%standard_options, @_) >> || die "bad command line"; >> >> - # override GetOptions default for :i >> - $verbose = 1 if (defined($verbose) && $verbose==0); >> $verbose ||= 0; # stop complaints about undefined var in numeric comparison >> } >> >> >> > > > > What is weird is that the only change has been to move this from > run_build.pl into PGBuild::Options::fetch_options. Those two lines have > been in run_build.pl for many years: > > 2cdd46ae    (Andrew Dunstan 2004-09-24 20:22:32 +0000   111)$verbose=1 > if (defined($verbose) && $verbose==0); > 4307d647    (Andrew Dunstan 2005-12-23 16:55:53 +0000   112)$verbose ||= > 0; # stop complaints about undefined var in numeric comparison > > and the lines you showed come from run_build.pl. > > The rationale for the move was to make the flag sanely available to > other programs, specifically run_branches.pl. > > So it's very odd. I'll do some experimenting. > Hah! I have it. How annoying. It's run_branches passing the adjusted value through to run_build. Will fix. cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services