On Tue, 14 Jan 2025 at 12:32, Tom Lane wrote:
> Robins Tharakan writes:
> > The error seems to be around "annobin.so" and so it may be about how
> > gcc is being compiled (not sure). While I figure out if GCC compilation
> > needs work, I thought to bring it up here since v16+ seems to work fine
Robins Tharakan writes:
> Unrelated, parula has been failing the libperl test (only v15 and older),
> for the past
> 3 weeks - to clarify, this test started to fail (~18 days ago) before I
> fixed the
> 'RemoveIPC' configuration (~5 days ago), so this is unrelated to that
> change.
> https://buil
Hi Alexander,
On Sun, 22 Dec 2024 at 17:57, Robins Tharakan wrote:
>
> So if that's a key reason here, then probably by this time next week
things should
> settle down. I've begun setting it correctly (2 done with a few more to
go) - although
> given that some machines are at work, I'll try
On Thu, 9 Jan 2025 at 15:30, Alexander Lakhin wrote:
>
> Maybe you could try to reproduce such failures without buildfarm client,
just
> by running select_parallel, for example, with the attached patch applied.
> I mean running `make check` with parallel_schedule like:
> ...
> Or
> TESTS="test_set
Hello Robins,
22.12.2024 09:27, Robins Tharakan wrote:
- The only info about leafhopper may be relevant is that it's one of the newest machines (Graviton4) so it comes with
a recent hardware / kernel / stock gcc 11.4.1.
Could you please take a look at leafhopper. which is producing weird tes
On Sun, Dec 22, 2024 at 08:00:00AM +0200, Alexander Lakhin wrote:
> and batta:
> sid | gcc recent | aarch64 | michael [ a t ] paquier.xyz
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=batta&dt=2024-12-16%2008%3A05%3A04
I suspect that this one has been caused by me, as I have logged int
Hi Alexander,
Thanks for collating this list.
I'll try to add as much as I know, in hopes that it helps.
On Sun, 22 Dec 2024 at 16:30, Alexander Lakhin wrote:
> I'd like to bring your attention to multiple buildfarm failures, which
> occurred this month, on master only, caused by "could not ope
