Re: regression tests fails with llvm22 - Mailing list pgsql-hackers

From Matheus Alcantara
Subject Re: regression tests fails with llvm22
Date
Msg-id bcf92e99-b5ca-452d-b0dd-fe1b3c46176f@gmail.com
Whole thread Raw
In response to regression tests fails with llvm22  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: regression tests fails with llvm22
List pgsql-hackers
On 03/03/26 02:06, Pavel Stehule wrote:
> Hi
> 
> I did upgrade today
> 
> pavel@nemesis:~/src/postgresql$ uname -a
> Linux nemesis 6.19.5-300.fc44.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Feb 28
> 00:00:53 UTC 2026 x86_64 GNU/Linux
> 
> pavel@nemesis:~/src/postgresql$ llvm-config --version
> 22.1.0
> 
> and regression tests fails
> 
> cat
> /home/pavel/src/postgresql/src/test/isolation/output_iso/regression.diffs
> diff -U3
> /home/pavel/src/postgresql/src/test/isolation/expected/multixact-stats.out
> /home/pavel/src/postgresql/src/test/isolation/output_iso/results/multixact-stats.out
> ---
> /home/pavel/src/postgresql/src/test/isolation/expected/multixact-stats.out
> 2026-02-19 05:31:42.337867043 +0100
> +++
> /home/pavel/src/postgresql/src/test/isolation/output_iso/results/multixact-stats.out
> 2026-03-03 06:00:45.850492589 +0100
> @@ -68,22 +68,11 @@
>       ]
>     ) AS r(assertion, ok);
> 
> -assertion               |ok
> -------------------------+--
> -is_init_mxids           |t
> -is_init_members         |t
> -is_init_oldest_mxid     |t
> -is_init_oldest_off      |t
> -is_oldest_mxid_nondec_01|t
> -is_oldest_mxid_nondec_12|t
> -is_oldest_off_nondec_01 |t
> -is_oldest_off_nondec_12 |t
> -is_members_increased_ge1|t
> -is_mxids_nondec_01      |t
> -is_mxids_nondec_12      |
> -is_members_nondec_01    |
> -is_members_nondec_12    |
> -(13 rows)
> +FATAL:  fatal llvm error: Broken module found, compilation aborted!
> +server closed the connection unexpectedly
> + This probably means the server terminated abnormally
> + before or while processing the request.
> 
>   step s1_commit: COMMIT;
> -step s2_commit: COMMIT;
> +failed to send query for step s2_commit: no connection to the server
> +
> 

I think that [1] is about to fix this.

[1] 
https://www.postgresql.org/message-id/CA%2BhUKGJTumad75o8Zao-LFseEbt%3DenbUFCM7LZVV%3Dc8yg2i7dg%40mail.gmail.com

--
Matheus Alcantara
EDB: https://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Henson Choi
Date:
Subject: Re: Row pattern recognition
Next
From: Jakub Wartak
Date:
Subject: Re: pg_plan_advice (now with transparent SQL plan performance overrides - pg_stash_advice)