Re: seawasp failing, maybe in glibc allocator

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: seawasp failing, maybe in glibc allocator
Date: 2021-05-22 08:08:46
Message-ID: alpine.DEB.2.22.394.2105221001170.165418@pseudo
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Banck 2021-05-22 08:10:17 Re: Commitfest app vs. pgsql-docs
Previous Message Dilip Kumar 2021-05-22 06:40:22 Re: Race condition in recovery?