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

On Sun, Mar 4, 2018 at 2:34 PM, Andrew Dunstan
<andrew(dot)dunstan(at)2ndquadrant(dot)com> wrote:
> On Sun, Mar 4, 2018 at 12:42 AM, Peter Eisentraut
> <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>> 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
>>
>
> Something like this should do the trick.

[ tiny patch]

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.

cheers

andrew

--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services