Re: seawasp failing, maybe in glibc allocator

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


Hello Thomas,

> Seawasp should turn green on its next run.

Hopefully.

It is not scheduled very soon because Tom complained about the induced
noise in one buildfarm report, so I put the check to once a week.

I changed it to start a run in a few minutes. I've rescheduled to once a
day after that (previous schedule was a check every hour).

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2021-06-26 06:47:34 Re: pgsql: Fix pattern matching logic for logs in TAP tests of pgbench
Previous Message Fabien COELHO 2021-06-26 05:42:07 Re: Some incorrect logs in TAP tests of pgbench