From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
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:11:05 |
Message-ID: | 11510.1397617865@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
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 ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2014-04-16 03:23:32 | Re: [COMMITTERS] pgsql: Add TAP tests for client programs |
Previous Message | Peter Eisentraut | 2014-04-16 03:03:11 | Re: [COMMITTERS] pgsql: Add TAP tests for client programs |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2014-04-16 03:16:46 | Re: New option in pg_basebackup to exclude pg_log files during base backup |
Previous Message | Peter Eisentraut | 2014-04-16 03:03:11 | Re: [COMMITTERS] pgsql: Add TAP tests for client programs |