Re: what's going on with lapwing?

On Mon, Mar 3, 2025 at 6:09 PM Julien Rouhaud <rjuju123(at)gmail(dot)com> wrote:
> Well, AFAIK the usual habit when something is broken and a buildfarm cilent
> upgrade is needed is to warn the buildfarm owners. There was an email
> yesterday for installing libcurl which I did. There was an email before last
> release for possibly stuck tests which I checked. There was no such email to
> ask to update the client, so I'm not sure why you expected me to do so?
>
> Apart from that, commit aeb8ea361 is from january 24, and the latest buildfarm
> client release (18) is from november, did I miss something?

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.

> Yes it's me. I'm not sure why it's such a mystery as I've been answering for
> it for many years. Having an alias is useful to me as I can redirect it to
> some private mailbox with less traffic and therefore react promptly in case of
> any problem.

Buildfarm members are labelled with an email address, not a name. I
don't magically know the names of all the people who correspond to
those email addresses. I've learned some of them over time, but I
didn't recognize rjuju.net.

--
Robert Haas
EDB: http://www.enterprisedb.com