| From: | Robins Tharakan <tharakan(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Sam James <sam(at)gentoo(dot)org>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Build failure with GCC 15 (defaults to -std=gnu23) |
| Date: | 2024-12-13 02:01:34 |
| Message-ID: | CAEP4nAyOKW+CLHrFDHw1e6fjEG+urL2x1DSeFiU8vnaGsOrV1g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, 13 Dec 2024 at 11:52, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robins Tharakan <tharakan(at)gmail(dot)com> writes:
> > It's been a few days since alligator lit up the buildfarm red. IMHO at
> this
> > point, it is just noise. So I've reduced its v16+ build frequency to
> daily
> > (instead of a few minutes). I'll revert that once gcc is fixed upstream.
>
> Looks like alligator just went green with the 20241212 gcc build.
>
Nice! Just forced REL_17_STABLE / REL_16_STABLE and they are past
that failure point too (still running).
For now I've restored the original build frequency for these branches.
-
robins
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robins Tharakan | 2024-12-13 02:16:25 | Re: Build failure with GCC 15 (defaults to -std=gnu23) |
| Previous Message | Tom Lane | 2024-12-13 01:21:53 | Re: Build failure with GCC 15 (defaults to -std=gnu23) |