| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andrew Dunstan <adunstan(at)postgresql(dot)org>, pgbuildfarm(at)rjuju(dot)net |
| Subject: | Re: what's going on with lapwing? |
| Date: | 2025-03-06 21:59:16 |
| Message-ID: | CA+TgmoboN2DbkXRKnwmANp1WBNug0GYPgm5g2Zb-2m0+VusNxQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Mar 6, 2025 at 4:54 PM Melanie Plageman
<melanieplageman(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matheus Alcantara | 2025-03-06 22:02:39 | Re: PoC. The saving of the compiled jit-code in the plan cache |
| Previous Message | Jacob Champion | 2025-03-06 21:58:55 | Re: dblink: Add SCRAM pass-through authentication |