Re: pgsql: Remove command checks in tests of pg_basebackup and pg_receivewa

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Remove command checks in tests of pg_basebackup and pg_receivewa
Date: 2022-05-01 13:15:46
Message-ID: Ym6IAq48gBBm5Ujv@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Sat, Apr 30, 2022 at 04:52:54PM -0400, Andrew Dunstan wrote:
> This appears to have been misconceived, at least in the case of MSVC
> builds, as I have just discovered. It is entirely possible to have the
> lz4 libraries installed and build with them but not have the .exe, and
> unlike the configure case the MSVC build system doesn't conduct any test
> for it, resulting in a nasty looking TAP test failure. I assume similar
> failures are possible with zstd and maybe gzip.

Okay, we could change the code of vcregress.pl so as the different ENV
commands (tar, zstd, lz4 or gzip) are assigned as follows for the sake
of the tests:
- If a ENV value is available, trust the environment/user and rely on
it.
- If a ENV value is not available, try to look for it in the
environment by launching a simple $command --version (-version should
be fine across all the commands currently in need of coverage?).
-- On failure, set ENV{command} to an empty string.
-- On success, set ENV{command} = "$command"

Does something like this look better to you?
--
Michael

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2022-05-01 14:18:37 Re: pgsql: Remove command checks in tests of pg_basebackup and pg_receivewa
Previous Message Andrew Dunstan 2022-04-30 20:52:54 Re: pgsql: Remove command checks in tests of pg_basebackup and pg_receivewa