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?
Has anyone tried to reproduce this on other platforms?
It'd be interesting to know which updates were applied to skink's
host before the first failing run.
regards, tom lane