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 1of3rT-0000jA-Pt for pgsql-hackers@arkaria.postgresql.org; Sun, 02 Oct 2022 18:38:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1of3rR-0000d6-TU for pgsql-hackers@arkaria.postgresql.org; Sun, 02 Oct 2022 18:38:45 +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 1of3rR-0000cx-Fe for pgsql-hackers@lists.postgresql.org; Sun, 02 Oct 2022 18:38:45 +0000 Received: from mail-io1-xd2b.google.com ([2607:f8b0:4864:20::d2b]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1of3rM-0008Q2-JF for pgsql-hackers@postgresql.org; Sun, 02 Oct 2022 18:38:45 +0000 Received: by mail-io1-xd2b.google.com with SMTP id 138so6737774iou.9 for ; Sun, 02 Oct 2022 11:38:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20210112.gappssmtp.com; s=20210112; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:from:to:cc:subject:date; bh=Wc+53zxt5eJMpsq6BUHXg/xDAvW4RogYsZAAiv2/6gI=; b=Ki4F6NUJEwFdiOKSHdqCnXphfzX7bn9AylGQ/OxsSV3uuD1iMB7ge0E+Gf/wSdks2L zemIw/CKbWOU5Z+aH3SqLuCwVEgTbVwkeyk0u26uBdwM9wYs3PvKC2+xItVhAfmZJIFd XRbrk2dv97pGJ5EEc02tzxWN8KHpAd6gZKciO2o8MnLWwwOv0zMcHgoHg3Os3+muV8LP v4Uc9RA48tFFK4hIslLICYFSHJogB5yumlS4T4s3hvjJUlcrIcIW1WpH6/SkekKle7/I 7hUuoZj1u+nWqawP2+PXS5KlVCPR+LDZAoXd0CgNOx82nXMaknTN1HSSu7NX5Qh9550W q6yA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date; bh=Wc+53zxt5eJMpsq6BUHXg/xDAvW4RogYsZAAiv2/6gI=; b=MQg9vpK6su09zY7zdVlaK3VC5RtyBsVhEeHIfrzsaOaGfiVgV+/nwgbohpIgKn4tOO 2GrvcWptDdZ/G8oAk7fBuM/qoQg7YfwmuHVN8NpAy9GukueIfHpAWeDNSzlCzdrM9G1c XqjhPd7wyQaqw3bASI69Xaj9kHFbhgc6QtznxIbjyufxZw0wTGW3LVShiYlILybJJWnO Ks6m3FwJoThugOEq/ulFZ4CguRja/EpoBTNSsMhDwa8TKdxuZGpyGTen2dZooTFEnlSF +sR6ju+cxSQ4O+BDWLHA2d3UCURRx/LNfehngPbMRaVcj+uXt5kcUrUymM7XWAl6Sr/D gi+g== X-Gm-Message-State: ACrzQf1bthn3I0E18jyAstcmyjq87gvikHVXqMdghyZnHyTFxx/xkLtJ gMtx/NWgMJoQcQh5Kow4o5Oacg== X-Google-Smtp-Source: AMsMyM4hweCk3uSrY5VtXq8/41reV9EX0whigIR1yyHEMspTJhANn4MBUbxMUAPAMvrznwEztFhKsw== X-Received: by 2002:a05:6638:d04:b0:363:36d7:6696 with SMTP id q4-20020a0566380d0400b0036336d76696mr509156jaj.63.1664735918604; Sun, 02 Oct 2022 11:38:38 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id j8-20020a0566022cc800b006a153f7e34asm3666717iow.6.2022.10.02.11.38.37 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 02 Oct 2022 11:38:38 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 33126800784; Sun, 2 Oct 2022 13:38:37 -0500 (CDT) Date: Sun, 2 Oct 2022 13:38:37 -0500 From: Justin Pryzby To: Andres Freund Cc: Peter Eisentraut , Peter Geoghegan , "wangw.fnst@fujitsu.com" , Tom Lane , Nathan Bossart , Andrew Dunstan , Thomas Munro , samay sharma , Nazir Bilal Yavuz , pgsql-hackers@postgresql.org Subject: Re: [RFC] building postgres with meson - v13 Message-ID: <20221002183837.GD7745@telsasoft.com> References: <20220922202809.4touie37lfafyabw@awork3.anarazel.de> <20220922223729.GA721620@nathanxps13> <2298281.1664041949@sss.pgh.pa.us> <20220924180955.2hevwoniwsj2q2tm@awork3.anarazel.de> <20220926163516.ftxjmoljjwyy4m2q@awork3.anarazel.de> <20220926194435.4hhrwu7d6anrapc3@awork3.anarazel.de> <20220927011951.j3h4o7n6bhf7dwau@awork3.anarazel.de> <20221002172520.GC7745@telsasoft.com> <20221002180530.fkhl6kpx734dlmow@awork3.anarazel.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221002180530.fkhl6kpx734dlmow@awork3.anarazel.de> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sun, Oct 02, 2022 at 11:05:30AM -0700, Andres Freund wrote: > > Also, you wrote "rm -fr build" between building for gcc and clang, but > > since they run in an "always" block, it'd be better to use separate > > dirs, to allow seeing logs for the the all (failed) tasks, in case the > > last one succeeds. > > Hm, when are logs important for CompilerWarnings? I don't think we even > collect any? Using a different builddir for the "sibling" tests (i.e. the two > gcc and the two clang tests) would increase the times a bit because we'd > regenerate the bison files etc. > > I guess it'll look a bit cleaner to use a build-gcc and a build-clang, just to > get rid of the irregularity of needing that rm -rf. The build logs are important when hacking on .cirrus.yml itself. You're right that we don't normally save logs for CompilerWarnings; one or another (unpublished) patch of mine adds that, and then also needed to change to use separate dirs in order to debug building while experimenting with your patch to use meson. -- Justin