public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: [email protected]
Subject: Operational note: possible infinite loop in today's HEAD testing
Date: Mon, 26 Sep 2016 21:16:45 -0400
Message-ID: <[email protected]> (raw)
List-Unsubscribe:  <mailto:[email protected]?body=unsub%20buildfarm-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

view thread (2+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected]
  Subject: Re: Operational note: possible infinite loop in today's HEAD testing
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox