Subject: Re: Rewriting the test of pg_upgrade as a TAP test - take two
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
References: <20180126080026.GI17847@paquier.xyz>
 <7d040dbb-33f3-edb7-b13d-0f4ab607af46@2ndquadrant.com>
 <CAA8=A79KwJ4Yt3C9LAMt9-i+N=jDP2Z+NoE0qh069BetX0kmCw@mail.gmail.com>
 <CAA8=A7-xR98DkqdoTAui3i4Y17xJPrMrxYGr9KDh0Hs0qVYjMg@mail.gmail.com>
Cc: Michael Paquier <michael.paquier@gmail.com>,
 Postgres hackers <pgsql-hackers@postgresql.org>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Organization: 2ndQuadrant
Message-ID: <08724398-ce66-9236-18fc-b7f22a15c017@2ndquadrant.com>
Date: Tue, 6 Mar 2018 15:13:46 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0)
 Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: 
 <CAA8=A7-xR98DkqdoTAui3i4Y17xJPrMrxYGr9KDh0Hs0qVYjMg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 3/4/18 16:09, Andrew Dunstan wrote:
>>> 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.

> Pushed with a bug fix. See
> <https://github.com/PGBuildFarm/client-code/commit/826d450eff05d15c8bb3c5b2728da5328634a588>
> 
> If you want to do this soon I can put out a Buildfarm Client release
> fairly quickly.

I think the dependency is mostly the other way around.  How quickly
would build farm owners install the upgrade?

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