Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nN0x8-0000eq-Au for pgsql-hackers@arkaria.postgresql.org; Wed, 23 Feb 2022 23:21:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nN0x7-0002Ti-5w for pgsql-hackers@arkaria.postgresql.org; Wed, 23 Feb 2022 23:21:45 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nN0x6-0002Pz-S8 for pgsql-hackers@lists.postgresql.org; Wed, 23 Feb 2022 23:21:44 +0000 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nN0x4-0001gg-03 for pgsql-hackers@postgresql.org; Wed, 23 Feb 2022 23:21:43 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 94DE13201C39; Wed, 23 Feb 2022 18:21:39 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Wed, 23 Feb 2022 18:21:39 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=tW+/2LP+2bXVmo7qQ4tDFhUger8WcBA3jYhMiC2OS Zg=; b=IrdwyIIRnrPBBxzuoXr3sTW6gp1qIhTCRld3MVCRz0jPCmzIl30tO6mww tycpejJH5wapqx34RjMH4nyQAXZaeR7s1nnxIzlkASNin7PAqEvnt/Mgw9lB4XN+ qka7as04UVIun/WNwhugHcmHXnGbxTkSG1pC93o3wryOG9Y103aCA7piHs2oBh3c UuWC3bZf7h7Q8biJw+H5btQDLGOa0875508n79BfHf20v36KbGF+fJT5YFK85/TC P2naVmCwuDXfYYlOtgK3htaMNMwG9c1YJDHnDbaEPhlshPAlbRdYYwxjPvszTskA qG4fk7OjZoqa41ltEGZCZR2Imau6g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrledugddtkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvghtvghr ucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrh hprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeefjeegheetuefhveevudel ueeftdejteeiffetvdduhfdtieefgfeutedtveeggfenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghuthes vghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 23 Feb 2022 18:21:38 -0500 (EST) Message-ID: <4f4c04c2-f23c-6668-1b24-224fc6478bfd@enterprisedb.com> Date: Thu, 24 Feb 2022 00:21:36 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.6.0 Subject: Re: convert libpq uri-regress tests to tap test Content-Language: en-US To: Tom Lane Cc: Andres Freund , pgsql-hackers@postgresql.org References: <20220223203031.ezrd73ohvjgfksow@alap3.anarazel.de> <1261838.1645657117@sss.pgh.pa.us> From: Peter Eisentraut In-Reply-To: <1261838.1645657117@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 23.02.22 23:58, Tom Lane wrote: > Peter Eisentraut writes: >> On 23.02.22 21:30, Andres Freund wrote: >>> Where would we want that test to live? Right now we have the slightly odd >>> convention that some tap tests live in src/test/{misc,modules,...}. But >>> e.g. frontend binary ones are below src/bin/. > >> libpq TAP tests should be in src/interfaces/libpq/t/. > >> I think there were issues that the build farm wouldn't pick up a test >> located there, but that should be fixed rather than worked around. > > That's failing to account for the fact that a libpq test can't > really be a pure-perl TAP test; you need some C code to drive the > library. I don't agree with intermixing such code with libpq > itself, independently of any buildsystem issues (which there > might well be). Such things could be put under src/interfaces/libpq/test, or some other subdirectory. We already have src/interfaces/ecpg/test. > So I think the design of putting such tests under > src/modules is fine. I don't get what the rationale for that would be. libpq tests are not "modules" of any kind. If I'm working on libpq, I want to do make && make check inside the libpq source directory.