Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gkH8I-00061G-Qq for pgsql-hackers@arkaria.postgresql.org; Thu, 17 Jan 2019 23:31:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gkH8G-0000oL-9F for pgsql-hackers@arkaria.postgresql.org; Thu, 17 Jan 2019 23:31:32 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gkH8F-0000Xd-TH for pgsql-hackers@lists.postgresql.org; Thu, 17 Jan 2019 23:31:32 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gkH8D-0003uI-FF for pgsql-hackers@lists.postgresql.org; Thu, 17 Jan 2019 23:31:30 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x0HNVRRk019617; Thu, 17 Jan 2019 18:31:27 -0500 From: Tom Lane To: =?UTF-8?Q?Mikael_Kjellstr=c3=b6m?= cc: pgsql-hackers@lists.postgresql.org Subject: Re: PSA: we lack TAP test coverage on NetBSD and OpenBSD In-reply-to: References: <9427.1547701450@sss.pgh.pa.us> <22802.1547759781@sss.pgh.pa.us> <0a6ece1f-8175-e873-c459-c3a8fd18ad71@mksoft.nu> <26513.1547761358@sss.pgh.pa.us> <1d5a693b-1491-0527-44e8-ac21301f37a8@mksoft.nu> <17004.1547763782@sss.pgh.pa.us> Comments: In-reply-to =?UTF-8?Q?Mikael_Kjellstr=c3=b6m?= message dated "Fri, 18 Jan 2019 00:10:01 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <19615.1547767887.1@sss.pgh.pa.us> Date: Thu, 17 Jan 2019 18:31:27 -0500 Message-ID: <19616.1547767887@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk =?UTF-8?Q?Mikael_Kjellstr=c3=b6m?= writes: > And now also the NetBSD machine failed on pgbenchCheck. Indeed, as expected. > should I leave it as it is for now? Please. I'll push a fix for the broken test case in a bit --- I just wanted to confirm that somebody else's machines agreed that it's broken. regards, tom lane