Hi, On Sun, 14 Jun 2026 at 01:27, Tom Lane <[email protected]> wrote: > > =?utf-8?Q?=C3=81lvaro?= Herrera <[email protected]> writes: > > For some reason, a couple of animals running gcc-15 or newer > > (leafhopper, massasauga, parula) appear to be failing now because of > > this. > > They just started failing a day or two ago, so it's hard to blame > it on any code change we made. I see that all three of those animals > are using "experimental" nightly builds of gcc, so it's reasonable to > assume that gcc's git tip is broken. Or maybe something needs updated > in the recipe for replacing their gcc builds.
Earlier, since gcc HEAD was too noisy, I moved them all to gcc v15 assuming it'd be better. The gcc build script has been stable and there's been no change in any of the machines recently, so I also wouldn't be surprised if it is gcc again. For now, I've taken them all offline and unless someone has a better idea, I'll switch them to stay pinned to the recentmost gcc release version - rationale being that if a tagged gcc release is buggy, it may be interesting to know about. - robins | robins.in
