public inbox for [email protected]
help / color / mirror / Atom feedOperational note: possible infinite loop in today's HEAD testing
2+ messages / 2 participants
[nested] [flat]
* Operational note: possible infinite loop in today's HEAD testing
@ 2016-09-27 01:16 Tom Lane <[email protected]>
2016-09-28 15:58 ` Re: Operational note: possible infinite loop in today's HEAD testing Andrew Dunstan <[email protected]>
0 siblings, 1 reply; 2+ messages in thread
From: Tom Lane @ 2016-09-27 01:16 UTC (permalink / raw)
To: buildfarm-members
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.)
regards, tom lane
--
Sent via buildfarm-members mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/buildfarm-members
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Operational note: possible infinite loop in today's HEAD testing
2016-09-27 01:16 Operational note: possible infinite loop in today's HEAD testing Tom Lane <[email protected]>
@ 2016-09-28 15:58 ` Andrew Dunstan <[email protected]>
0 siblings, 0 replies; 2+ messages in thread
From: Andrew Dunstan @ 2016-09-28 15:58 UTC (permalink / raw)
To: Tom Lane <[email protected]>; 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
--
Sent via buildfarm-members mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/buildfarm-members
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2016-09-28 15:58 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2016-09-27 01:16 Operational note: possible infinite loop in today's HEAD testing Tom Lane <[email protected]>
2016-09-28 15:58 ` Andrew Dunstan <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox