On Tue, Jan 3, 2012 at 6:29 PM, Peter Eisentraut <pete...@gmx.net> wrote: > On mån, 2012-01-02 at 17:27 -0500, Andrew Dunstan wrote: >> >> On 01/02/2012 04:37 PM, Peter Eisentraut wrote: >> > On mån, 2012-01-02 at 15:55 -0500, Andrew Dunstan wrote: >> >> On 01/02/2012 03:12 PM, Peter Eisentraut wrote: >> >>> pg_regress: Replace exit_nicely() with exit() plus atexit() hook >> >>> >> >> This appears to have broken the buildfarm. >> > I think you mean it has caused the build to fail on some buildfarm >> > members. AFAICT, the buildfarm itself is still intact. >> >> This is hardly the first use of this idiom. > > But it's about as helpful as a bug report saying "help it's broken".
I don't see why. Normally you can just go to buildfarm.postgresql.org and see which machines are failing and at what stage, and the view the stage logs to see the specific errors. It's not the best web interface I've ever seen, but it's not *that* bad. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
