Re: MSVC SSL test failure

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Lars Kanis <lars(at)greiz-reinsdorf(dot)de>
Subject: Re: MSVC SSL test failure
Date: 2021-12-07 16:25:15
Message-ID: 3497326.1638894315@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alexander Lakhin <exclusion(at)gmail(dot)com> writes:
> It seems that the test failure rate may depend on the specs/environment.

No surprise there, since the issue is almost surely timing-dependent.

> shutdown(MyProcPort->sock, SD_SEND) apparently fixes the issue, I've got
> 83 successful runs, but then iteration 84 unfortunately failed:
> t/001_ssltests.pl .. 106/110
> #   Failed test 'intermediate client certificate is missing: matches'
> #   at t/001_ssltests.pl line 608.
> #                   'psql: error: connection to server at "127.0.0.1",
> port 63187 failed: could not receive data from server: Software caused
> connection abort (0x00002745/10053)
> # SSL SYSCALL error: Software caused connection abort (0x00002745/10053)
> # could not send startup packet: No error (0x00000000/0)'
> #     doesn't match '(?^:SSL error: tlsv1 alert unknown ca)'
> # Looks like you failed 1 test of 110.

Hmm. I wonder whether using SD_BOTH behaves any differently.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2021-12-07 16:33:38 Re: pg_dump versus ancient server versions
Previous Message Robert Haas 2021-12-07 16:19:27 Re: ExecTypeSetColNames is fundamentally broken