Subject: Re: Operational note: possible infinite loop in
 today's HEAD testing
To: Tom Lane <tgl@sss.pgh.pa.us>, buildfarm-members@postgresql.org
References: <28557.1474939005@sss.pgh.pa.us>
From: Andrew Dunstan <andrew@dunslane.net>
Message-ID: <cc38b2bc-7f7d-6574-ab81-db1d6b21b30f@dunslane.net>
Date: Wed, 28 Sep 2016 11:58:19 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <28557.1474939005@sss.pgh.pa.us>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: buildfarm-members-owner@postgresql.org


On 09/26/2016 09:16 PM, Tom Lane wrote:
> If you run any PG buildfarm critters that are configured with
> --enable-tap-tests, you might want to check to see if they're caught
> in an infinite loop in pgbench :-(.  If so, just kill -9 that process,
> and the next run should recover OK.
>
> The cause is a platform-dependent bug introduced in commit 12788ae49
> and fixed in 9779bda86.
>
> A look through the buildfarm status says that the only members using
> --enable-tap-tests that haven't reported in successfully despite the bug
> are hamster, jacana, and topminnow.  But I'm sending this out more
> widely just in case I missed somebody's machine.
>
> (Andrew: I wonder if we should have a sanity limit on how long buildfarm
> runs are allowed to take.  Not sure what to put the limit at, though.)


Maybe, it would have to be configurable. We actually have some code for 
doing that sort of thing from back in the CVS days when we used to get 
CVS hangs, so it shouldn't be hard.


cheers

andrew


-- 
Sent via buildfarm-members mailing list (buildfarm-members@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/buildfarm-members