From: Tom Lane <tgl@sss.pgh.pa.us>
To: buildfarm-members@postgresql.org
Subject: Operational note: possible infinite loop in today's HEAD testing
Date: Mon, 26 Sep 2016 21:16:45 -0400
Message-ID: <28557.1474939005@sss.pgh.pa.us>
Precedence: bulk
Sender: buildfarm-members-owner@postgresql.org

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 (buildfarm-members@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/buildfarm-members