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

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

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

Tom Lane-2
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.

Branch
------
REL_10_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/e1b4135cfef656f6b8c42e86b0c0a7cbafebdd92

Modified Files
--------------
contrib/pgcrypto/expected/pgp-compression_1.out | 28 +++++++++++++++++++++++++
1 file changed, 28 insertions(+)

Reply | Threaded
Open this post in threaded view
|

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

Michael Paquier-2
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

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

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

Tom Lane-2
Michael Paquier <[hidden email]> writes:
> 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?

Yeah, I just boot it up every week or two ... machine is too noisy to keep
running all the time.

                        regards, tom lane