Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cUefz-0007dI-HV for pgsql-hackers@arkaria.postgresql.org; Fri, 20 Jan 2017 19:16:43 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cUefy-0001km-OH for pgsql-hackers@arkaria.postgresql.org; Fri, 20 Jan 2017 19:16:42 +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.84_2) (envelope-from ) id 1cUeea-00007w-8U for pgsql-hackers@postgresql.org; Fri, 20 Jan 2017 19:15:16 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cUeeX-0007Z0-18 for pgsql-hackers@postgresql.org; Fri, 20 Jan 2017 19:15:15 +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 v0KJF8ls021213; Fri, 20 Jan 2017 14:15:08 -0500 From: Tom Lane To: Alvaro Herrera cc: Pavan Deolasee , pgsql-hackers Subject: Re: Failure in commit_ts tap tests In-reply-to: <20170120182702.tjjk2mh3t5keansh@alvherre.pgsql> References: <20170120182702.tjjk2mh3t5keansh@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Fri, 20 Jan 2017 15:27:02 -0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <21211.1484939708.1@sss.pgh.pa.us> Date: Fri, 20 Jan 2017 14:15:08 -0500 Message-ID: <21212.1484939708@sss.pgh.pa.us> X-Pg-Spam-Score: -5.1 (-----) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Alvaro Herrera writes: > Hmm. The test works fine for me, even if it should be obvious that the > use of the != operator is wrong. I don't understand why it causes a > failure only for you. Even more interesting, the warning appears as-expected in stripped down test cases, eg $ perl -e 'use warnings; use Test::More; ok("Foo" ne "bar", "ok");' ok 1 - ok # Tests were run but no plan was declared and done_testing() was not seen. $ perl -e 'use warnings; use Test::More; ok("Foo" != "bar", "ok");' Argument "bar" isn't numeric in numeric ne (!=) at -e line 1. Argument "Foo" isn't numeric in numeric ne (!=) at -e line 1. not ok 1 - ok # Failed test 'ok' # at -e line 1. # Tests were run but no plan was declared and done_testing() was not seen. I really don't understand why this complains but the same perl version is happy with (the previous coding in) 004_restart.pl. Perl bug? regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers