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 1o8RpO-0004pe-Gu for pgsql-hackers@arkaria.postgresql.org; Mon, 04 Jul 2022 19:33:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1o8RpM-00081u-A4 for pgsql-hackers@arkaria.postgresql.org; Mon, 04 Jul 2022 19:33:48 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o8RpL-0007vj-As for pgsql-hackers@lists.postgresql.org; Mon, 04 Jul 2022 19:33:48 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o8RpF-0001Hx-TF for pgsql-hackers@lists.postgresql.org; Mon, 04 Jul 2022 19:33:46 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id B89EF5C00F1; Mon, 4 Jul 2022 15:33:38 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Mon, 04 Jul 2022 15:33:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id: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; t=1656963218; x= 1657049618; bh=4n+8vg76ITYvxr7AK9RI6dNNf+cREhIk/xCFqsjNqog=; b=x cOqmew4vi6tvThtT2cBVV3hp7hk58An6kkF7ShXQdMV3IkQ+AiYwt+kcBcNa8Izg JmOiUxGhY461O1QTJJjmWpgYhiK8IfGYY3zbfmFgK45xRtN3fJjKAXF6H6m47+MQ vYUqiTiSsuw7OUEqkTNA57h3KA+JLc3Wf8BUO7GwTNbzgKEAR5oJqvyHzQS2eWqa 1cPF1q0WrhHiLb0frGvhMrQKlbwBF0YLZBGllHP31vfdHXxL/bDiPP0nmGgkyb56 Xv9vKmzoRXkpo2m37H+PKrF1Z3g9Mi+MZKP1rZQb3N0U300/nktNwQqRpBNl8WWy WVlGeO1nLbStrlZe8BVWA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrudehledgudeflecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfevfhfhjggtgfesthejredttdefjeenucfhrhhomheprfgv thgvrhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdrvghishgvnhhtrhgruhhtsegvnh htvghrphhrihhsvggusgdrtghomheqnecuggftrfgrthhtvghrnhepheelffeggedujeet iefhleetuddvieffhfffvdejvdffgeejkeduleduheduieefnecuvehluhhsthgvrhfuih iivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvrhdrvghishgvnhhtrhgr uhhtsegvnhhtvghrphhrihhsvggusgdrtghomh X-ME-Proxy: Feedback-ID: i131946ab:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 4 Jul 2022 15:33:37 -0400 (EDT) Message-ID: Date: Mon, 4 Jul 2022 21:33:36 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Subject: Re: TAP output format in pg_regress Content-Language: en-US To: Tom Lane Cc: Daniel Gustafsson , Andres Freund , PostgreSQL Developers References: <49A54862-C682-4B60-9155-05F178FA79DC@yesql.se> <20220321234924.kcc3q26o7sx6rnfa@alap3.anarazel.de> <489D2B5A-B26F-4918-BC07-B426329169E3@yesql.se> <5e6bc6a6-0a4e-109d-2b7d-c286dc58d609@enterprisedb.com> <1558373.1656945577@sss.pgh.pa.us> From: Peter Eisentraut In-Reply-To: <1558373.1656945577@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 04.07.22 16:39, Tom Lane wrote: > Probably is, because this is bad: > >> ... The proposed default format now hides the >> fact that some tests are started in parallel. I remember the last time >> I wanted to tweak the output of the parallel tests, people were very >> attached to the particular timing and spacing of the current output. So >> I'm not sure people will like this. > and so is this: > >> The timing output is very popular. Where is that in the TAP output? > Both of those things are fairly critical for test development. You > need to know what else might be running in parallel with a test case, > and you need to know whether you just bloated the runtime unreasonably. I don't think there is a reason these couldn't be shown in TAP output as well. Even if we keep the two output formats in parallel, it would be good if they showed the same set of information.