Re: what's going on with lapwing?

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Julien Rouhaud <rjuju123(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, pgbuildfarm(at)rjuju(dot)net
Subject: Re: what's going on with lapwing?
Date: 2025-03-04 14:19:35
Message-ID: 1a862070-e68e-4c99-bb99-84f0580a28da@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2025-03-03 Mo 6:12 PM, Tom Lane wrote:
> Julien Rouhaud<rjuju123(at)gmail(dot)com> writes:
>>> On Mon, Mar 3, 2025 at 2:53 PM Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)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.
>
>

Yeah, I try to avoid making too many releases, but I agree it's time to
push one.

cheers

andrew

--
Andrew Dunstan
EDB:https://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alex Friedman 2025-03-04 14:22:45 Re: Doc fix of aggressive vacuum threshold for multixact members storage
Previous Message Magnus Hagander 2025-03-04 14:12:18 Vacuum timing in pg_stat_all_tables