| From: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: Instability of phycodorus in pg_upgrade tests with JIT |
| Date: | 2025-10-16 19:00:00 |
| Message-ID: | 2b280c41-236d-4cd3-a7e3-ea86d5c1e257@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello Tom and Michael,
16.10.2025 02:39, Tom Lane wrote:
> Michael Paquier<michael(at)paquier(dot)xyz> writes:
>> I have spotted a couple of buildfarm failures for buildfarm member
>> phycodorus on REL_14_STABLE and REL_13_STABLE:
>> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=phycodurus&dt=2025-10-15%2009%3A12%3A36
> phycodorus seems to be running a remarkably ancient LLVM version.
> I wonder if we should just write these off as "probably an LLVM bug".
I collected all of such failures here:
https://wiki.postgresql.org/wiki/Known_Buildfarm_Test_Failures#check-pg_upgrade_fails_on_LLVM-enabled_animals_due_to_double_free_or_corruption
Masao-san was going to dig into that:
https://www.postgresql.org/message-id/CAHGQGwFcjccSYX+Ap8meEbCccUei-B4tmYsBFu4wMEixKi90fQ@mail.gmail.com
Best regards,
Alexander
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Alger | 2025-10-16 19:04:56 | Re: [PATCH] Add pg_get_trigger_ddl() to retrieve the CREATE TRIGGER statement |
| Previous Message | Robert Haas | 2025-10-16 18:59:48 | Re: Making pg_rewind faster |