Re: MSVC buildfarm critters are not running modules' TAP tests - Mailing list pgsql-hackers

From Tom Lane
Subject Re: MSVC buildfarm critters are not running modules' TAP tests
Date
Msg-id 17551.1567979940@sss.pgh.pa.us
Whole thread Raw
In response to Re: MSVC buildfarm critters are not running modules' TAP tests  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Responses Re: MSVC buildfarm critters are not running modules' TAP tests
List pgsql-hackers
Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
> On 9/8/19 12:07 PM, Tom Lane wrote:
>> It looks to me like the reason is that src/tools/msvc/vcregress.pl's
>> subroutine subdircheck isn't considering the possibility that
>> subdirectories of src/test/modules contain TAP tests.  The
>> same code is used for contrib, so several existing TAP tests
>> are being missed there too.

> Actually, I think vcregress.pl is OK, this is a gap in the buildfarm
> client's coverage that will be fixed when I make a new release.

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?

            regards, tom lane



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: pgsql: Use data directory inode number, not port, to select SysVresour
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Use data directory inode number, not port, to select SysV resour