Re: what's going on with lapwing?
Andrew Dunstan <andrew@dunslane.net>
From: Andrew Dunstan <andrew@dunslane.net>
To: Tom Lane <tgl@sss.pgh.pa.us>, Julien Rouhaud <rjuju123@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
pgbuildfarm@rjuju.net
Date: 2025-03-04T14:19:35Z
Lists: pgsql-hackers
On 2025-03-03 Mo 6:12 PM, Tom Lane wrote: > 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. > > 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
Commits
-
Revert workarounds for -Wmissing-braces false positives on old GCC
- 618c64ffd396 18.0 landed
-
Convert sepgsql tests to TAP
- aeb8ea361a0a 18.0 cited