From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Valgrind failures in Apply Launcher's bgworker_quickdie() exit |
Date: | 2018-12-14 02:15:19 |
Message-ID: | 8EA259F8-4F51-44AB-A827-101682B86E57@anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On December 13, 2018 6:01:04 PM PST, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> writes:
>> Since libcrypto.so is implicated, Andres asked me off-list if my
>> changes to random number state initialisation might be linked to
>> skink's failures beginning 12 or 15 days ago. It appears not, as it
>> was green for several runs after that commit.
>> ...
>> It's Debian unstable, which could be a factor. Bugs in glibc?
Note it's only failing on master...
>Has anyone tried to reproduce this on other platforms?
I recently also hit this locally, but since that's also Debian unstable... Note that removing openssl "fixed" the issue for me.
>It'd be interesting to know which updates were applied to skink's
>host before the first failing run.
I'll check the logs when I'm back at a real computer.
Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2018-12-14 02:52:03 | Re: slight tweaks to documentation about runtime pruning |
Previous Message | Tom Lane | 2018-12-14 02:01:04 | Re: Valgrind failures in Apply Launcher's bgworker_quickdie() exit |