From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: MSVC buildfarm critters are not running modules' TAP tests
Date: Sun, 08 Sep 2019 18:18:33 -0400
Message-ID: <18363.1567981113@sss.pgh.pa.us> (raw)
In-Reply-To: <688d32cf-19be-c8f0-f08b-fde25d15132e@2ndQuadrant.com>
References: <6628.1567958876@sss.pgh.pa.us>
<5e1113b9-e1a6-d68b-c05c-06e607a4cd5f@2ndQuadrant.com>
<17551.1567979940@sss.pgh.pa.us>
<688d32cf-19be-c8f0-f08b-fde25d15132e@2ndQuadrant.com>
Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
> On 9/8/19 5:59 PM, Tom Lane wrote:
>> Hm. Changing the buildfarm script would be an alternative way to
>> fix the issue so far as the buildfarm is concerned, but it doesn't
>> seem like it provides any useful way for one to manually invoke
>> the tests on Windows. Or am I missing something about how that's
>> usually done?
> The invocation is:
> vcregress.pl taptest [ PROVE_FLAGS=xxx ] directory
Sure, I saw that you can run one test that way ... but what do you
do when you want the equivalent of check-world?
(I'm surprised that vcregress hasn't already got a "world" option.
But at least there should be a determinate list of what you need
to run to get all the tests.)
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, andrew.dunstan@2ndquadrant.com, pgsql-hackers@lists.postgresql.org
Subject: Re: MSVC buildfarm critters are not running modules' TAP tests
In-Reply-To: <18363.1567981113@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox