From: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Subject: Re: PostgreSQL BuildFarm Client Release 9
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: buildfarm-members@postgresql.org
References: <ebd5fd3d-78dc-9ce4-0889-0a7c6580adac@2ndQuadrant.com>
 <30667.1542051948@sss.pgh.pa.us>
Message-ID: <0156912c-cfc8-4018-9d88-61353fbc97b5@2ndQuadrant.com>
Date: Mon, 12 Nov 2018 15:17:24 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.3.0
MIME-Version: 1.0
In-Reply-To: <30667.1542051948@sss.pgh.pa.us>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-MW
Precedence: bulk


On 11/12/18 2:45 PM, Tom Lane wrote:
> Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
>> Along with numerous fixes of minor bugs and a couple of not so minor
>> bugs, this release has the following features:
>> ...
>>    * automatically rerun 3 hours after a git failure, useful on back
>>      branches where commits can be infrequent
> Hm, I'm worried that this is mainly going to result in spamming the server
> with git-failure reports.  From what I've seen, those usually don't go
> away by themselves; they need manual action to resolve, and that's often
> not promptly forthcoming.
>
> 			


If the git failure persists it will be spamming the server anyway. It's 
when it stops failing and then doesn't see a git advance and hence 
doesn't clear the error that this is trying to clear up.


cheers


andrew


-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services