Re: TAP tests are badly named - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: TAP tests are badly named
Date
Msg-id 55CCB514.6000807@dunslane.net
Whole thread Raw
In response to Re: TAP tests are badly named  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: TAP tests are badly named  (Michael Paquier <michael.paquier@gmail.com>)
Re: TAP tests are badly named  (Noah Misch <noah@leadboat.com>)
List pgsql-hackers

On 08/01/2015 07:13 PM, Andrew Dunstan wrote:
>
> On 08/01/2015 04:44 PM, Noah Misch wrote:
>>
>>>> --enable-tap-tests is a reasonable configuration setting, because it's
>>>> about whether or not we have a TAP testing framework available, but I
>>>> think we should stop calling the bin tests "TAP tests" and we should
>>>> change the test name in vcregress.pl to a more appropriate name. In
>>>> the
>>>> buildfarm I'm calling the step "bin-check":
>>>> <http://www.pgbuildfarm.org/cgi-bin/show_stage_log.pl?nm=crake&dt=2015-07-30%2012%3A25%3A58&stg=bin-check>
>>>>
>>>> Thoughts?
>> While lack of granularity in vcregress.pl is hostile, with so much
>> about MSVC
>> development being hostile, this one is below my noise floor.
>
>
> Speaking with my buildfarm hat on, it's well above mine. And these
> changes make the situation worse quite gratuitously. Anyway, I'll fix it.
>
>
>


here's what I propose.

cheers

andrew



Attachment

pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: [COMMITTERS] pgsql: Further fixes for degenerate outer join clauses.
Next
From: Michael Paquier
Date:
Subject: Re: In-core regression tests for replication, cascading, archiving, PITR, etc.