| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | 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>, Andrew Dunstan <adunstan(at)postgresql(dot)org>, pgbuildfarm(at)rjuju(dot)net |
| Subject: | Re: what's going on with lapwing? |
| Date: | 2025-03-03 23:12:57 |
| Message-ID: | 4140821.1741043577@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2025-03-03 23:24:06 | Re: Parallel heap vacuum |
| Previous Message | Julien Rouhaud | 2025-03-03 23:08:56 | Re: what's going on with lapwing? |