Horton

Re: what's going on with lapwing?

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
From: Robert Haas <robertmhaas@gmail.com>
To: Melanie Plageman <melanieplageman@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Andrew Dunstan <andrew@dunslane.net>, Julien Rouhaud <rjuju123@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Andrew Dunstan <adunstan@postgresql.org>, pgbuildfarm@rjuju.net
Date: 2025-03-06T21:59:16Z
Lists: pgsql-hackers 
On Thu, Mar 6, 2025 at 4:54 PM Melanie Plageman
<melanieplageman@gmail.com> 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.

This is a problem for me, too, so I would also be happy about this.

-- 
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