Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1es7ts-00072d-5A for pgsql-hackers@arkaria.postgresql.org; Sat, 03 Mar 2018 14:12:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1es7tp-0000sV-On for pgsql-hackers@arkaria.postgresql.org; Sat, 03 Mar 2018 14:12:33 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1es7tp-0000sL-HY for pgsql-hackers@lists.postgresql.org; Sat, 03 Mar 2018 14:12:33 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1es7tl-0001Z0-Vf for pgsql-hackers@postgresql.org; Sat, 03 Mar 2018 14:12:32 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 4718820F20; Sat, 3 Mar 2018 09:12:28 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Sat, 03 Mar 2018 09:12:28 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=vEa7Ae AwVFUuYE0KCpz6Pdv599KqcalejOvmoQK0hy8=; b=R+bd7RhEGYdUwubZRvUzPS CNSrx1ENR6aNXsKvrEwPAZgiCVDtP2yAJyxt8E9PqmRoEkkTjD4x31+22amOUPx6 ztjk2S+FepPpIilZypm4F6PeizA+GxaBPy5NENTWXxVBrwz3NQQ0lL1fTZBuTqNy tCKWjBfDSB1q6diQF2yob2h2R1JiEB1H9yxSOil4xhF64wC6j6Lk/q08BSq0zwFK Ao6pV4XMhzTpGVXO9axltiM6vgwpKSRqs4e8LqTlaNAefPyyBfxnu65gxr0neLkc D/RaGHXuwCEdcRgpXGkClvZekrDtFP+bq8cDEtUL/wevz370V/Sd7qmsO7fc+sRg == X-ME-Sender: Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id 0634D7E321; Sat, 3 Mar 2018 09:12:28 -0500 (EST) Subject: Re: Rewriting the test of pg_upgrade as a TAP test - take two To: Michael Paquier , Postgres hackers References: <20180126080026.GI17847@paquier.xyz> From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <7d040dbb-33f3-edb7-b13d-0f4ab607af46@2ndquadrant.com> Date: Sat, 3 Mar 2018 09:12:27 -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: <20180126080026.GI17847@paquier.xyz> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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