public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: [email protected]
Subject: Please check for possibly-stuck PG buildfarm members
Date: Sat, 17 Mar 2018 15:53:49 -0400
Message-ID: <[email protected]> (raw)
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
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], [email protected]
Subject: Re: Please check for possibly-stuck PG buildfarm members
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