Re: Rewriting the test of pg_upgrade as a TAP test - take two - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Rewriting the test of pg_upgrade as a TAP test - take two
Date
Msg-id 7d040dbb-33f3-edb7-b13d-0f4ab607af46@2ndquadrant.com
Whole thread Raw
In response to Rewriting the test of pg_upgrade as a TAP test - take two  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Rewriting the test of pg_upgrade as a TAP test - take two  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
List pgsql-hackers
On 1/26/18 03:00, Michael Paquier wrote:
> As promised on a recent thread, here is a second tentative to switch
> pg_upgrade's test.sh into a TAP infrastructure.

AFAICT, this still has the same problem as the previous take, namely
that adding a TAP test suite to the pg_upgrade subdirectory will end up
with the build farm client running the pg_upgrade tests twice.  What we
likely need here is an update to the build farm client in conjunction
with this.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] GSOC'17 project introduction: Parallel COPY executionwith errors handling
Next
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] GSOC'17 project introduction: Parallel COPY executionwith errors handling