Re: what's going on with lapwing?

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Honestly, I just noticed that the buildfarm member in question had
> been red for over a month and I figured it was a setup issue of some
> kind. I guess I was wrong. It didn't cross my mind that a commit over
> a month ago had broken things and there had been no subsequent revert
> or buildfarm client release. I'm frankly quite astonished because Tom
> recently told me that I needed to fix something RIGHT NOW or else
> revert when the commit had been in the tree for two hours. Given that
> context, maybe you can understand why I thought it was unlikely that
> we were just chilling about this being broken after 38 days.

As far as that goes, there are degrees of buildfarm brokenness.

Right now we have three remaining animals that are affected by the
sepgsql issue (two of which seem to have been stopped awhile ago by
their owners), and the error is perfectly predictable/repeatable.
So it's easy to ignore.

At the point where I complained to you about that other problem,
it was looking like it might cause a quarter or a third of the
buildfarm to fail intermittently. Maybe I overestimated the
frequency of the failure, but if that was accurate it would have
resulted in a lot of fruitless double-checking of failures to
see if there was anything real underneath the noise. So I find
that sort of case much more painful.

But yeah, I thought we were overdue for a buildfarm release.
I'm pleased to see that Andrew just pushed one.

regards, tom lane