Re: Operational note: possible infinite loop in today's HEAD testing

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, buildfarm-members(at)postgresql(dot)org
Subject: Re: Operational note: possible infinite loop in today's HEAD testing
Date: 2016-09-28 15:58:19
Message-ID: cc38b2bc-7f7d-6574-ab81-db1d6b21b30f@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: buildfarm-members

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

In response to

Browse buildfarm-members by date

  From Date Subject
Next Message Andrew Dunstan 2016-10-12 00:24:34 buildfarm client release 4.18
Previous Message Tom Lane 2016-09-27 01:16:45 Operational note: possible infinite loop in today's HEAD testing