Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eXAEg-0007y7-CD for buildfarm-members@arkaria.postgresql.org; Thu, 04 Jan 2018 18:27:26 +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 1eXAEf-0008Ds-Uw for buildfarm-members@arkaria.postgresql.org; Thu, 04 Jan 2018 18:27:25 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eXAEf-0008Di-QQ for buildfarm-members@lists.postgresql.org; Thu, 04 Jan 2018 18:27:25 +0000 Received: from mail-yw0-x241.google.com ([2607:f8b0:4002:c05::241]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1eXAEb-00022b-NY for buildfarm-members@postgresql.org; Thu, 04 Jan 2018 18:27:25 +0000 Received: by mail-yw0-x241.google.com with SMTP id f1so902252ywd.8 for ; Thu, 04 Jan 2018 10:27:21 -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=+gFG0/65oaC7QlPDTWXatfxSE/Qko/qKafasWHbIWVE=; b=KO9zUZuUiFH8qKqcqjIItGv0kkyg9Zaf3PQLkgXi/s1Z1EEAR6dEX8rrAbTBVwEx5x Yq69KCLb35oEAhfHGsKcM46A1Ir0N4qkZ9FdI7W7jRjDfE62P/2+l/0rN2sKqcwQOgH4 +B7PS0FjPvQaatCT4vHySSxJabreqgFSU2igLdI/Ai/GgVxd5PhTY1LFDTQryhlXm2tp +zA1KEqBovv0pooKue39IQTwOehhUSZDH0BZ9y6vX3hQX7cCOORuI9mOmsmFiZd+T/c1 z+eHh/J0DUhmLeV14A+CPcPbXpLLeCCQ1QcKGaPDaKOw+DBpCvMnVxnXkTaLwcuQqkl6 ZOQA== 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=+gFG0/65oaC7QlPDTWXatfxSE/Qko/qKafasWHbIWVE=; b=WTCEfwDnybBR5JJTBTRYg4m1RNmuFNyKfCsDS93JxLmvsWC9c4ftmdCqozhlPf/ErC X8bjNknTqL+4VrxM1B2oBZUi+YjzvhWheVbIc1kO6ze2yLhEqz5fu56cSszoT6gCXvk7 OcI6l47/r8BZXTZvRjFPKbn2FYDBlltOYkqgWbhMJNI2ITZprpxULm2DQZyhDfpZR34Z gDoCIdd1xoQJqikHvjNCUhqurwLoLkP8Fe13lErC0dAIayqYRbNsHkXkFF3DmmUcKupj BJVfpqIL/To2RjdqlKMw+6p0uhwxRtVcr0o3te9B2Hqq05+CUWebcoGRXL9nDCAYgGRo 54MA== X-Gm-Message-State: AKGB3mIjaU84vuYbMviA1r6/kShsLEQh5h4dy/T82KyXkP34uoNlRX1Y xYMuJbnPzd3z30u0+MANJQQfMc4ibxrD2LQlPjUcbmHe5g0eNM1K+SSuBUxf2A5ofavL2WVQwF7 BpsVBY9Z28wWlvC0aoqxZ8u2Hqajb3hWlz0F7yL2HeGufM+/54ABCpcIHWrL/0JfB0oBkGOgber h5CZMko7sCq2PulBC0Mg== X-Google-Smtp-Source: ACJfBosJHmoXHwPtm94Yfaz4AaxKQiBqHUTB0W3WUp/u9gLV56xkDEj6t7tS8FyG5vvvY/WVaGjb9A== X-Received: by 10.129.235.17 with SMTP id n17mr428406ywm.41.1515090439275; Thu, 04 Jan 2018 10:27:19 -0800 (PST) Received: from [192.168.10.146] ([98.122.175.38]) by smtp.gmail.com with ESMTPSA id q129sm1634244ywc.73.2018.01.04.10.27.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Jan 2018 10:27:18 -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: Date: Thu, 4 Jan 2018 13:27: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: <9420.1515088313@sss.pgh.pa.us> 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 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. cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services