Re: what's going on with lapwing?

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>
To: Julien Rouhaud <rjuju123@gmail.com>
Cc: Andres Freund <andres@anarazel.de>, Tom Lane <tgl@sss.pgh.pa.us>, Andrew Dunstan <andrew@dunslane.net>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Andrew Dunstan <adunstan@postgresql.org>, pgbuildfarm@rjuju.net
Date: 2025-03-06T23:25:29Z
Lists: pgsql-hackers
On Thu, Mar 6, 2025 at 5:12 PM Julien Rouhaud <rjuju123@gmail.com> wrote:\
> I indeed don't want to keep lapwing up unless there is any value.  Note that it
> started to fail on 2 branches after the last buildfarm client update for
> reasons I don't understand.  Since everyone is complaining about lapwing
> already I will just turn it off.  If anyone is interested in keeping it up on
> REL_13_STABLE until its EOL (so for the next ~6 months) let me know.

We're not complaining, we're just discussing. :-)

In all seriousness, I appreciate the willingness of you and others to
run BF members and of Andrew to maintain the BF client. It's kind of a
thankless job, I'm sure, but will be much worse off as a project if
people just stop doing those things. Wanting to figure out how we can
do better or wondering whether a certain machine makes sense any more
doesn't translate into not appreciating the work.

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



Commits

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

  2. Convert sepgsql tests to TAP