Re: Rewriting the test of pg_upgrade as a TAP test - take two

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Rewriting the test of pg_upgrade as a TAP test - take two
Date: 2018-03-03 14:12:27
Message-ID: 7d040dbb-33f3-edb7-b13d-0f4ab607af46@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2018-03-03 14:30:02 Re: [HACKERS] GSOC'17 project introduction: Parallel COPY execution with errors handling
Previous Message Peter Eisentraut 2018-03-03 14:02:23 Re: [HACKERS] GSOC'17 project introduction: Parallel COPY execution with errors handling