From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: MSVC buildfarm critters are not running modules' TAP tests |
Date: | 2019-09-08 22:18:33 |
Message-ID: | 18363.1567981113@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2019-09-08 23:35:59 | Re: MSVC buildfarm critters are not running modules' TAP tests |
Previous Message | Andrew Dunstan | 2019-09-08 22:14:52 | Re: MSVC buildfarm critters are not running modules' TAP tests |