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

From Fabien COELHO
Subject Re: seawasp failing, maybe in glibc allocator
Date
Msg-id alpine.DEB.2.22.394.2105221001170.165418@pseudo
Whole thread Raw
In response to Re: seawasp failing, maybe in glibc allocator  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> 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.

Indeed, the full recompilation is triggered once a week, on Saturdays.

If the build fails for some reason the previous version is kept and I may 
or may not have time to look at it and try to fix it for some time after 
that, or I may happen that I do not notice the issue for some time…

-- 
Fabien.

pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: Race condition in recovery?
Next
From: Michael Banck
Date:
Subject: Re: Commitfest app vs. pgsql-docs