From: | Robins Tharakan <tharakan(at)gmail(dot)com> |
---|---|
To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org, tharar(at)amazon(dot)com |
Subject: | Re: Why is parula failing? |
Date: | 2024-05-16 10:48:43 |
Message-ID: | CAEP4nAzTOf5=HhWHu6bZObMhVJx8dkPMYgPhp27JYKnYd0RsVQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 14 May 2024 at 08:55, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> I've not seen any recent failures from Parula that relate to this
> issue. The last one seems to have been about 4 weeks ago.
>
> I'm now wondering if it's time to revert the debugging code added in
> 1db689715. Does anyone think differently?
>
Thanks for keeping an eye. Sadly the older machine was decommissioned
and thus parula hasn't been sending results to buildfarm the past few days.
I'll try to build a similar machine (but newer gcc etc.) and reopen this
thread in case I hit
something similar.
-
robins
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2024-05-16 11:35:29 | Re: GUC names in messages |
Previous Message | Jelte Fennema-Nio | 2024-05-16 10:41:50 | Re: PostgreSQL 17 Beta 1 release announcement draft |