Re: seawasp failing, maybe in glibc allocator - Mailing list pgsql-hackers

From Tom Lane
Subject Re: seawasp failing, maybe in glibc allocator
Date
Msg-id 166151.1621635534@sss.pgh.pa.us
Whole thread Raw
In response to Re: seawasp failing, maybe in glibc allocator  (Andres Freund <andres@anarazel.de>)
Responses Re: seawasp failing, maybe in glibc allocator
Re: seawasp failing, maybe in glibc allocator
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> Interesting. I tried this with a slightly older LLVM checkout
> (6f4f0afaa8ae), from 2021-04-20, contrib/ltree tests run without an
> issue, even if I force everything to be jitted+inlined+optimized. The
> git hash in the package version indicates the commit is from
> 2021-05-20. Upgrading my local checkout to see whether I can repro the
> problem. If I can we at least have a not too large bisection window...

We know that seawasp was okay as of

configure: using compiler=clang version 13.0.0 (https://github.com/llvm/llvm-project.git
f22d3813850f9e87c5204df6844a93b8c5db7730)

and not okay as of

configure: using compiler=clang version 13.0.0 (https://github.com/llvm/llvm-project.git
0e8f5e4a6864839d2292ec1ddfe48b6178c01f85)

so that should correspond to a window of about a week, if I gather
Fabien's update strategy correctly.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Subscription tests fail under CLOBBER_CACHE_ALWAYS
Next
From: Andres Freund
Date:
Subject: Re: seawasp failing, maybe in glibc allocator