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 1na8BX-0001Um-Im for pgsql-hackers@arkaria.postgresql.org; Fri, 01 Apr 2022 03:42:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1na8BV-0003YB-Dj for pgsql-hackers@arkaria.postgresql.org; Fri, 01 Apr 2022 03:42:49 +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 1na8BU-0003Y2-Nu for pgsql-hackers@lists.postgresql.org; Fri, 01 Apr 2022 03:42:48 +0000 Received: from mail-qv1-xf2c.google.com ([2607:f8b0:4864:20::f2c]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1na8BR-0002By-Rg for pgsql-hackers@lists.postgresql.org; Fri, 01 Apr 2022 03:42:47 +0000 Received: by mail-qv1-xf2c.google.com with SMTP id gh15so1132075qvb.8 for ; Thu, 31 Mar 2022 20:42:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=961RdFSRyAkg/Unj2mVX8DUwtdCePEdU01G3dG31CEw=; b=KI31Jl+SHY0Lhwe8uqvLS1Hh5A5jlrUwkiKmnRri8NaEPodG5QsyVQwrmXZ2ITf6c8 JbrLhrMT+qcpt3re8KfRYVjffDzI+CkYR7iR1MUAfnZPwpm02+nX5rqQVyKVtam5VjxE dGhtT9GFCabro9uaYR4Ar+2LJ+HVJc8fvIRns= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=961RdFSRyAkg/Unj2mVX8DUwtdCePEdU01G3dG31CEw=; b=n935ZKeKzk2g6trLGkCowiXUfXGs13dVFvR0fJen1S4qaaAgoX88gnXoetreeDNU+z uZ7Sm5YijpZDwjykQOJdwUqPc3oi2kd55IWGlFhU6pgADJk8D3gN8+MbJxKVUz9dvENF tc/qdpkq8lK2eIZcbCJqB14cYryOYaGs82AjE2+QcxtoyeDQsNYcEfUzr+mVYdaTPthZ a4V8HZn32YF+QX+ecSM4y9VBVl/c7vcCKRM4IgOr1Mz8CpWobUl5i2i+PXfe7Ey85Yeu rrmunBGl/pjjlconiJF2G3rVyXUlUgSEOgaUDNutmWtlym8F7HTsOxt4Ywfh+1HEO6Ym Kn4Q== X-Gm-Message-State: AOAM530pDCpn40qfy9nMg8tWO1mDv4UbqK8KLUbIcQsNWhrpLdV6Ad5l coRE0Bgceb6qyyz45aeEKOQSFw== X-Google-Smtp-Source: ABdhPJxq2BfLOs6ooTQ47RvgLmSmrPXUGJi2JJjTkxy9ILHyWUnazAnd7EwuhCuNkFI+t27AV1Lydw== X-Received: by 2002:ad4:5de6:0:b0:441:6595:72cd with SMTP id jn6-20020ad45de6000000b00441659572cdmr6715150qvb.73.1648784564876; Thu, 31 Mar 2022 20:42:44 -0700 (PDT) Received: from rfd.leadboat.com ([2600:1702:a20:5750::2e]) by smtp.gmail.com with ESMTPSA id u22-20020a05622a199600b002eb841fcb6dsm959074qtc.73.2022.03.31.20.42.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 31 Mar 2022 20:42:44 -0700 (PDT) Date: Thu, 31 Mar 2022 20:42:41 -0700 From: Noah Misch To: Michael Paquier Cc: Tom Lane , Andres Freund , Thomas Munro , Julien Rouhaud , Andrew Dunstan , Postgres hackers Subject: Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set Message-ID: <20220401034241.GA3682158@rfd.leadboat.com> References: <20220302080729.q6wej3zlyaorjhri@alap3.anarazel.de> <502623.1648702814@sss.pgh.pa.us> <20220331053616.u446wsr732quuzer@alap3.anarazel.de> <547429.1648734590@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Apr 01, 2022 at 10:16:48AM +0900, Michael Paquier wrote: > On Thu, Mar 31, 2022 at 09:49:50AM -0400, Tom Lane wrote: > > Well, let's go ahead with it and see what happens. If it's too > > much of a mess we can always revert. > > Okay, done after an extra round of self-review. I have finished by > tweaking a couple of comments, and adjusted further TESTING to explain > what needs to be done to have a dump compatible with the test. Let's > now see what goes wrong. The REL_14 buildfarm client did not grab logs from the first failure: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=wrasse&dt=2022-04-01%2001%3A39%3A04 The failure looked like this: # Running: diff -q /export/home/nm/farm/studio64v12_6/HEAD/pgsql.build/src/bin/pg_upgrade/tmp_check/tmp_test_lPFv/dump1.sql /export/home/nm/farm/studio64v12_6/HEAD/pgsql.build/src/bin/pg_upgrade/tmp_check/tmp_test_lPFv/dump2.sql /usr/bin/diff: illegal option -- q usage: diff [-bitw] [-c | -e | -f | -h | -n | -u] file1 file2 diff [-bitw] [-C number | -U number] file1 file2 diff [-bitw] [-D string] file1 file2 diff [-bitw] [-c | -e | -f | -h | -n | -u] [-l] [-r] [-s] [-S name] directory1 directory2 not ok 4 - old and new dump match after pg_upgrade