From: Tom Lane <tgl@sss.pgh.pa.us>
To: buildfarm-members@lists.postgresql.org
Subject: Please check for possibly-stuck PG buildfarm members
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <18488.1521316429.1@sss.pgh.pa.us>
Date: Sat, 17 Mar 2018 15:53:49 -0400
Message-ID: <18489.1521316429@sss.pgh.pa.us>
Precedence: bulk

On 2017-12-31 I added a new regression test to exercise some formerly
untested code in plpgsql, and it turns out that the addition exposed a
compiler-dependent bug that would send the test into an infinite loop.
Buildfarm member fulmar, for one, has been stuck since then; we only
noticed when its test output file filled up the disk :-(.

I've now pushed a patch that should fix the underlying problem.
If you don't routinely monitor your buildfarm member(s), please check to
see if any have been stuck building HEAD since January.  A look at the
buildfarm webpage suggests that at least aholehole, dunlin, leech,
markhor, mastodon, and treepie might be suffering effects of this, as
they've not reported in for roughly the right amount of time.

			regards, tom lane