Postgres Pro
Downloads
Home   >   mailing lists

Thread: what's going on with lapwing?

what's going on with lapwing?

From
Robert Haas
Date:
lapwing has been failing sepgsql-check for over a month, but there's
no log file:


https://buildfarm.postgresql.org/cgi-bin/show_stage_log.pl?nm=lapwing&dt=2025-03-03%2016%3A29%3A50&stg=contrib-sepgsql-check

I feel like something must be broken with logfile collection in the
buildfarm client, because I keep seeing failures like this where
there's no log to view. It's hard to know whether this is a
configuration issue with this BF member or whether something actually
needs fixing. In any case, we should try to figure out what's going on
here.

Apologies if this has been discussed elsewhere and I have missed it.
Pointers appreciated.

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

Re: what's going on with lapwing?

From
Tom Lane
Date:
Robert Haas <robertmhaas@gmail.com> writes:
> lapwing has been failing sepgsql-check for over a month, but there's
> no log file:

I believe it hasn't been updated with the buildfarm client changes
needed to run sepgsql-check since aeb8ea361.

            regards, tom lane

Re: what's going on with lapwing?

From
Robert Haas
Date:
On Mon, Mar 3, 2025 at 2:53 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
> > lapwing has been failing sepgsql-check for over a month, but there's
> > no log file:
>
> I believe it hasn't been updated with the buildfarm client changes
> needed to run sepgsql-check since aeb8ea361.

OK, thanks. The owner is pgbuildfarm@rjuju.net, which I'm guessing
might be Julien Rouhaud, but not sure? It would be good to get that
updated, especially with the end of the release cycle hard upon us.

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

Re: what's going on with lapwing?

From
Julien Rouhaud
Date:
On Mon, Mar 03, 2025 at 03:52:30PM -0500, Robert Haas wrote:
> On Mon, Mar 3, 2025 at 2:53 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > Robert Haas <robertmhaas@gmail.com> writes:
> > > lapwing has been failing sepgsql-check for over a month, but there's
> > > no log file:
> >
> > I believe it hasn't been updated with the buildfarm client changes
> > needed to run sepgsql-check since aeb8ea361.

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?

> 
> OK, thanks. The owner is pgbuildfarm@rjuju.net, which I'm guessing
> might be Julien Rouhaud, but not sure?

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.

Re: what's going on with lapwing?

From
Tom Lane
Date:
Julien Rouhaud <rjuju123@gmail.com> writes:
>> On Mon, Mar 3, 2025 at 2:53 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> I believe it hasn't been updated with the buildfarm client changes
>>> needed to run sepgsql-check since aeb8ea361.

> 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?

Yeah, I think a new buildfarm release is overdue.  We have this issue
affecting sepgsql-check, and we have the TestUpgradeXversion changes
that are necessary for that still to work, and it's not great to
expect owners to run hand-patched scripts.

            regards, tom lane