Re: what's going on with lapwing?

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Julien Rouhaud <rjuju123@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Andrew Dunstan <adunstan@postgresql.org>, pgbuildfarm@rjuju.net
Date: 2025-03-03T23:12:57Z
Lists: pgsql-hackers
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



Commits

  1. Revert workarounds for -Wmissing-braces false positives on old GCC

  2. Convert sepgsql tests to TAP