Justin Pryzby writes:
> I think this is still failing
> https://cirrus-ci.com/task/6142528721256448
Sigh ... misleading formatting led me to see one log_like as
belonging to a connect_ok test, when it belongs to a connect_fails.
Fixed, thanks.
regards, tom lane
On Sat, Jul 16, 2022 at 06:26:57PM -0400, Tom Lane wrote:
> Andres Freund writes:
> > On 2022-07-16 17:33:47 -0400, Tom Lane wrote:
> >> Anyway, if Peter doesn't answer pretty soon I'll go do that.
>
> > It's about midnight in Germany, so unlikely to come soon...
>
> Done now.
I think this is s
Andres Freund writes:
> On 2022-07-16 17:33:47 -0400, Tom Lane wrote:
>> Anyway, if Peter doesn't answer pretty soon I'll go do that.
> It's about midnight in Germany, so unlikely to come soon...
Done now.
regards, tom lane
Hi,
On 2022-07-16 17:33:47 -0400, Tom Lane wrote:
> Andres Freund writes:
> > Yea, it's quite annoying. I think it might be worth to not wait for Peter to
> > chime in, but to just add a skip to the test for now?
>
> I was thinking of commenting out the log_like parts of the affected
> tests. M
Andres Freund writes:
> On 2022-07-16 10:45:29 -0400, Tom Lane wrote:
>> Looking at the cfbot, an annoyingly large percentage of current runs
>> are being broken by this. I think we need to do this as a stopgap:
>>> (2) abandon attempting to test this particular behavior.
> Yea, it's quite annoy
Hi,
On 2022-07-16 10:45:29 -0400, Tom Lane wrote:
> > Justin Pryzby writes:
> >> It failed for me just now: https://cirrus-ci.com/task/6502388730167296
>
> Looking at the cfbot, an annoyingly large percentage of current runs
> are being broken by this. I think we need to do this as a stopgap:
>
> Justin Pryzby writes:
>> It failed for me just now: https://cirrus-ci.com/task/6502388730167296
Looking at the cfbot, an annoyingly large percentage of current runs
are being broken by this. I think we need to do this as a stopgap:
> (2) abandon attempting to test this particular behavior.
I
Justin Pryzby writes:
> On Sat, Jul 16, 2022 at 01:57:25PM +0200, Peter Eisentraut wrote:
>> Isn't the cfbot using the same thing?
> It's using the same thing, so I suppose the failure is intermittent.
> It failed for me just now: https://cirrus-ci.com/task/6502388730167296
It looks like a timin
On Sat, Jul 16, 2022 at 01:57:25PM +0200, Peter Eisentraut wrote:
> On 16.07.22 13:37, Justin Pryzby wrote:
> > On Fri, Jul 15, 2022 at 03:35:28PM +, Peter Eisentraut wrote:
> > > Log details for client certificate failures
> >
> > This seems to be causing cfbot/linux to fail since yesterday.
On 16.07.22 13:37, Justin Pryzby wrote:
On Fri, Jul 15, 2022 at 03:35:28PM +, Peter Eisentraut wrote:
Log details for client certificate failures
This seems to be causing cfbot/linux to fail since yesterday.
Hmm, the Cirrus CI build works for me:
https://cirrus-ci.com/task/6520112718020
On Fri, Jul 15, 2022 at 03:35:28PM +, Peter Eisentraut wrote:
> Log details for client certificate failures
This seems to be causing cfbot/linux to fail since yesterday.
--
Justin
Log details for client certificate failures
Currently, debugging client certificate verification failures is
mostly limited to looking at the TLS alert code on the client side.
For simple deployments, sometimes it's enough to see "sslv3 alert
certificate revoked" and know exactly what needs to be
12 matches
Mail list logo
