Re: what's going on with lapwing?

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andrew Dunstan <adunstan(at)postgresql(dot)org>, pgbuildfarm(at)rjuju(dot)net
Subject: Re: what's going on with lapwing?
Date: 2025-03-04 14:26:38
Message-ID: Z8cNnr5gbmXyotJ1@jrouhaud
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 04, 2025 at 08:33:46AM -0500, Robert Haas wrote:
> 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, I do remember the 2 threads and I totally understand. On my side I know
that I don't have as much time as I'd like to contribute but I at least make
sure that I don't leave my animal broken because of something on my side. So I
did try to check when I received the first failure notifications, also saw that
there were no logs, found a few other animals with the same symptoms and
concluded that it would eventually be resolved either with a fix or some
instructions on the buildfarm client side or something. I did check again a
few days ago when I was that nothing was pushed anymore on that branch only,
saw that it was the same on other animals, got confused and gave up.
>
> > 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.

Ah sorry, I thought that the "rjuju" was a poor enough alias (which I more or
less use everywhere) that it would be recognisable. In any case I do receive
the emails so I can reply, just not from that address.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2025-03-04 14:26:40 Re: Next commitfest app release is planned for March 18th
Previous Message Andrei Lepikhov 2025-03-04 14:26:07 Re: Expand applicability of aggregate's sortop optimization