Re: what's going on with lapwing? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: what's going on with lapwing?
Date
Msg-id 0163b30e-8529-43fe-a99e-33dbd4418d56@eisentraut.org
Whole thread Raw
In response to Re: what's going on with lapwing?  (Melanie Plageman <melanieplageman@gmail.com>)
List pgsql-hackers
On 06.03.25 22:54, Melanie Plageman wrote:
> One thing I've been wishing for recently is access to the discussion
> and lore around individual buildfarm animals in a consolidated place.
> As a new committer, I haven't been part of all of these discussions
> over the last N years and so if an animal goes red, I can look through
> the buildfarm status history to see what kind of failures it has had
> for the last ~6 months, but it doesn't tell me if that machine is
> known for failing because of an outdated OS or some other
> platform-specific or hardware-specific issue.

I'm not sure there is more than that to it.  There is at any given time 
necessarily a trailing edge system, which is where you tend to run into 
trouble if you try to use compiler or library features past some 
invisible boundary, and which also tend to have flaky hardware and 
perhaps limited resources in general, and so you might also tend to see 
some more test instability there.

That used to be an HP-UX 10 system, and then later it was an OpenBSD on 
Sparc system, and now it's seemingly this one, and perhaps there were a 
few in between, and there will be a new one soon.  But this keeps 
moving, and the lore from more than 12 months ago is probably not that 
useful here.




pgsql-hackers by date:

Previous
From: Anthonin Bonnefoy
Date:
Subject: Re: Add Pipelining support in psql
Next
From: Amit Kapila
Date:
Subject: Re: Selectively invalidate caches in pgoutput module