From: Daniel Gustafsson <daniel@yesql.se>
To: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Add TAP tests for contrib/sslinfo
Date: Tue, 30 Nov 2021 17:58:05 +0100
Message-ID: <FB603D1D-2F48-48E1-B1BB-4DEF95DAF393@yesql.se> (raw)
In-Reply-To: <058AAA2B-06CA-4D1C-8D24-B9EA6632C072@yesql.se>
References: <E1ms0iG-00050P-1G@gemulon.postgresql.org>
<058AAA2B-06CA-4D1C-8D24-B9EA6632C072@yesql.se>
> On 30 Nov 2021, at 17:40, Daniel Gustafsson <daniel@yesql.se> wrote:
>
>> On 30 Nov 2021, at 11:50, Daniel Gustafsson <dgustafsson@postgresql.org> wrote:
>>
>> Add TAP tests for contrib/sslinfo
>
> This just failed on fairywren with the below:
>
> not ok 1 - certificate authorization succeeds with correct client cert in PEM format
>
> # Failed test 'certificate authorization succeeds with correct client cert in PEM format'
> # at t/003_sslinfo.pl line 71.
> # got: '2'
> # expected: '0'
> connection error: 'psql: error: connection to server at "127.0.0.1", port 60695 failed: certificate present, but not private key file "/home/pgrunner/bf/root/HEAD/pgsql.build/src/test/ssl/tmp_check/client_ext.key"'
> while running 'psql -XAtq -d sslrootcert=ssl/root+server_ca.crt sslmode=require dbname=certdb hostaddr=127.0.0.1 user=ssltestuser sslcert=ssl/client_ext.crt sslkey=/home/pgrunner/bf/root/HEAD/pgsql.build/src/test/ssl/tmp_check/client_ext.key -f - -v ON_ERROR_STOP=1' at /home/pgrunner/bf/root/HEAD/pgsql.build/../pgsql/src/test/perl/PostgreSQL/Test/Cluster.pm line 1807.
>
> ..which is odd, since the key was copied to tmp_check earlier in the test and
> passed that. The 001 and 002 tests do the same kind of copying and there it
> worked, so it seems a tad odd. Does anyone have any ideas on insights here?
Scratch that, all the copying for tests 001 through 003 had failed. I clearly
need another coffee.
The question still stands though, does anyone have any ideas on what could've
happened as I'm currently drawing a blank?
--
Daniel Gustafsson https://vmware.com/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-committers@postgresql.org
Cc: daniel@yesql.se
Subject: Re: pgsql: Add TAP tests for contrib/sslinfo
In-Reply-To: <FB603D1D-2F48-48E1-B1BB-4DEF95DAF393@yesql.se>
References: <E1ms0iG-00050P-1G@gemulon.postgresql.org> <058AAA2B-06CA-4D1C-8D24-B9EA6632C072@yesql.se> <FB603D1D-2F48-48E1-B1BB-4DEF95DAF393@yesql.se>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox