Re: pgsql: Adjust pgcrypto's expected test results for --disable-strong-ran

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Adjust pgcrypto's expected test results for --disable-strong-ran
Date: 2020-08-03 01:54:24
Message-ID: 20200803015424.GI3317@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Sun, Aug 02, 2020 at 03:00:21PM +0000, Tom Lane wrote:
> Adjust pgcrypto's expected test results for --disable-strong-random.
>
> These files were missed when commit a3ab7a707 added a new test query.
> Understandable considering these files no longer exist in HEAD.
> Per buildfarm member pademelon.

Oops. Thanks, Tom. I did not notice the failure. pademelon does not
run automatically, explaining why there is a hole of two weeks in the
report, right?
--
Michael

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2020-08-03 04:39:21 pgsql: Add %P to log_line_prefix for parallel group leader
Previous Message Thomas Munro 2020-08-03 00:51:18 pgsql: Fix rare failure in LDAP tests.