Re: Making background psql nicer to use in tap tests

Daniel Gustafsson <daniel@yesql.se>

From: Daniel Gustafsson <daniel@yesql.se>
To: Andres Freund <andres@anarazel.de>
Cc: Andrew Dunstan <andrew@dunslane.net>, Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Melanie Plageman <melanieplageman@gmail.com>, Amit Kapila <amit.kapila16@gmail.com>, mikael.kjellstrom@gmail.com
Date: 2023-04-07T21:01:47Z
Lists: pgsql-hackers
> On 7 Apr 2023, at 22:24, Daniel Gustafsson <daniel@yesql.se> wrote:
> 
>> On 7 Apr 2023, at 18:14, Daniel Gustafsson <daniel@yesql.se> wrote:
>>> On 7 Apr 2023, at 17:04, Andres Freund <andres@anarazel.de> wrote:
> 
>>> Afaict the failures are purely about patch 2, not 1, right?
>> 
>> Correct.  The attached v6 wraps the interactive_psql test in a SKIP block with
>> a conditional on IO::Pty being available.
> 
> This version was green in the CFBot, so I ended up pushing it after some
> documentation fixups and polish.

Looks like morepork wasn't happy with the interactive \password test.

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=morepork&dt=2023-04-07%2020%3A30%3A29

Looking into why the timer timed out in that test.

--
Daniel Gustafsson




Commits

  1. Fix missing installation/uninstallation rules for BackgroundPsql.pm

  2. Backport BackgroundPsql perl test module

  3. Add missing uninstallation rule for BackgroundPsql.pm

  4. Fix missing installation rules for BackgroundPsql.pm

  5. Skip \password TAP test on old IPC::Run versions

  6. Test SCRAM iteration changes with psql \password

  7. Refactor background psql TAP functions