| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
| Subject: | Re: Failures with gcd functions with GCC snapshots GCC and -O3 (?) |
| Date: | 2021-06-18 21:46:00 |
| Message-ID: | 1334331.1624052760@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> writes:
>> It'd sure be nice if seawasp stopped spamming the buildfarm failure log,
>> too.
> There was a silent API breakage (same API, different behavior, how nice…)
> in llvm main that Andres figured out, which will have to be fixed at some
> point, so this is reminder that it is still a todo…
If it were *our* todo, that would be one thing; but it isn't.
> Not sure when a fix is
> planned, though. I'm afraid portability may require that different code is
> executed depending on llvm version. Or maybe we should wrestle a revert on
> llvm side? Hmmm…
> So I'm not very confident that the noise will go away quickly, sorry.
Could you please just shut down the animal until that's dealt with?
It's extremely unpleasant to have to root through a lot of useless
failures to find the ones that might be of interest. Right now
serinus and seawasp are degrading this report nearly to uselessness:
https://buildfarm.postgresql.org/cgi-bin/show_failures.pl
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2021-06-18 22:17:20 | Re: Failures with gcd functions with GCC snapshots GCC and -O3 (?) |
| Previous Message | Fabien COELHO | 2021-06-18 21:37:44 | Re: Version reporting in pgbench |