Re: [COMMITTERS] pgsql: Add TAP tests for client programs

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Add TAP tests for client programs
Date: 2014-04-16 03:23:32
Message-ID: 534DF7B4.8040006@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 4/15/14, 11:11 PM, Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>> On 4/14/14, 10:30 PM, Andrew Dunstan wrote:
>>> Yes. It probably won't be a huge change, but it will need a bit of code.
>
>> It might be more future-proof if the build farm just called make
>> check-world and used some other way to identify the individual tests in
>> that output. Otherwise, we'll need a new build farm release every time
>> a test suite is added.
>
> That argument would be more convincing if "make check-world" worked
> on Windows ...

What about it doesn't work on Windows?

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Heikki Linnakangas 2014-04-16 07:29:07 pgsql: Use correctly-sized buffer when zero-filling a WAL file.
Previous Message Tom Lane 2014-04-16 03:11:05 Re: [COMMITTERS] pgsql: Add TAP tests for client programs

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2014-04-16 03:32:59 Re: Create function prototype as part of PG_FUNCTION_INFO_V1
Previous Message sure.postgres 2014-04-16 03:17:20 The question about the type numeric