Re: what's going on with lapwing?
Andrew Dunstan <andrew@dunslane.net>
From: Andrew Dunstan <andrew@dunslane.net>
To: Robert Haas <robertmhaas@gmail.com>, Julien Rouhaud <rjuju123@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
Andrew Dunstan <adunstan@postgresql.org>, pgbuildfarm@rjuju.net
Date: 2025-03-06T16:57:05Z
Lists: pgsql-hackers
On 2025-03-06 Th 10:45 AM, Robert Haas wrote: > On Wed, Mar 5, 2025 at 9:49 PM Julien Rouhaud <rjuju123@gmail.com> wrote: >> FWIW I installed the client version 19.1 this morning and forced a run on HEAD >> and lapwing is back to green. > Thanks, appreciate it. > > By the way, is there a particular reason why we're keeping Debian 7 > coverage in the buildfarm? I don't want to be in a huge rush to kill > platforms people still care about, but it was pointed out to me > off-list that this is quite an old release -- it seems Debian 7 was > first released in 2013, last released in 2016, EOL in 2018. I assume > that not too many people are going to install a PostgreSQL release > that comes out in 2025 on an OS that's been EOL for 7 years (or 12 > years if the BF page is correct that this is actually Debian 7.0). > Somewhat oddly, I see that we have coverage for Debian 9, 11, 12, and > 13, but not 8 or 10. Is there a theory behind all of this or is the > current situation somewhat accidental? > Fairly accidental, I think. We do have a project at EDB at fill in certain gaps in buildfarm coverage, so maybe we can reduce the incidence of such accidents. 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