Re: can we add subscription TAP test option "vcregress subscriptioncheck" for MSVC builds?

From: Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: can we add subscription TAP test option "vcregress subscriptioncheck" for MSVC builds?
Date: 2021-12-12 23:38:53
Message-ID: CAC+AXB0xn8eJoX6QOvODArJ-15PtQ63fKkCC+7S9oX4vtRk26w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 21, 2021 at 7:21 AM Bharath Rupireddy <
bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:

>
> Here's the documentation v1 patch that I've come up with. Please review it.
>
> There's a typo:
+ To run an arbitrary TAP test set, run <command>vcregress
taptest</command>
+ comamnd. For example, use the following command for running subcription
TAP
+ tests:
s/comamnd/command/

But also the wording, I like better what vcregress prints as help, so
something like:
+ You can use <command>vcregress taptest TEST_DIR</command> to run an
+ arbitrary TAP test set, where TEST_DIR is a required argument pointing
to
+ the directory where the tests reside. For example, use the following
+ command for running the subcription TAP tests:

Regards,

Juan José Santamaría Flecha

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2021-12-12 23:41:13 Re: [PATCH] pg_stat_toast
Previous Message Gunnar "Nick" Bluth 2021-12-12 23:00:23 Re: [PATCH] pg_stat_toast