Re: pgsql: Refactor all TAP test suites doing connection checks

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: Refactor all TAP test suites doing connection checks
Date: 2021-04-05 22:43:07
Message-ID: YGuSe6Q484Eshj2n@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Mon, Apr 05, 2021 at 10:57:22AM -0400, Tom Lane wrote:
> Some of the buildfarm seems not to like this. gaur failed here:

Thanks. I did not notice these.

> I didn't look at the code, but I bet this is similar to the race
> conditions we've seen before where a server process may exit before
> the perl test script finishes stuffing a command down the pipe.

Hmm. Those failures refer to the 5th and 8th tests of
001_password.pl where connect_ok() is used. The only logical
differences compared to the previous code are:
- The addition of on_error_stop in connect_ok() to ignore any errors
- The fact that this now defines a SQL query (was undef previously).
- $Test::Builder::Level
So, the problem is with on_error_stop. That's not necessary anyway,
but I am a bit surprised that this would be an issue. I'll apply that
to see if it fixes the issue. If it does not, a revert would be
better at this stage.
--
Michael

Attachment Content-Type Size
fix-auth-failure.patch text/x-diff 392 bytes

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2021-04-05 22:57:47 Re: pgsql: Refactor all TAP test suites doing connection checks
Previous Message Tom Lane 2021-04-05 22:42:46 pgsql: Support INCLUDE'd columns in SP-GiST.