Re: [HACKERS] Rewriting the test of pg_upgrade as a TAP test - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Rewriting the test of pg_upgrade as a TAP test
Date
Msg-id 29945.1504709090@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Rewriting the test of pg_upgrade as a TAP test  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: [HACKERS] Rewriting the test of pg_upgrade as a TAP test  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> Peter Eisentraut wrote:
>> We also need to have a plan for handling the build farm.  Maybe keep the
>> vcregress.pl upgradecheck target as a thin wrapper for the time being?

> The buildfarm already runs "make check" in src/bin/ when TAP tests are
> enabled, which should be enough to trigger the rewritten test, no?

I think Peter's on about the Windows case.  Not sure how that's handled,
but it's not "make check".
        regards, tom lane



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan
Next
From: Beena Emerson
Date:
Subject: Re: [HACKERS] increasing the default WAL segment size