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 1pZwa9-000088-Iv for pgsql-hackers@arkaria.postgresql.org; Wed, 08 Mar 2023 16:24:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pZwa8-0005RG-7n for pgsql-hackers@arkaria.postgresql.org; Wed, 08 Mar 2023 16:24:00 +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 1pZwa7-0005R4-3n for pgsql-hackers@lists.postgresql.org; Wed, 08 Mar 2023 16:23:59 +0000 Received: from new3-smtp.messagingengine.com ([66.111.4.229]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pZwa3-0006ER-CZ for pgsql-hackers@lists.postgresql.org; Wed, 08 Mar 2023 16:23:58 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailnew.nyi.internal (Postfix) with ESMTP id F290858204C; Wed, 8 Mar 2023 11:23:50 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 08 Mar 2023 11:23:50 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type: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=fm1; t= 1678292630; x=1678299830; bh=Ij7xahcQesSvM+qkA601GfuzdhfWpyjK1dU yApSL9KY=; b=cbjwcX4ZVN8Uk+08l6NVQj/aCjJvNNOFMQ2+aW3KISd/m2IFuR3 94MjyTkuRxWnwt9uh+Yb/VRa3pOTvDu1B5jkeoMjIZYQB0kZVqeMXgTefctkYgt0 VYmGVbbq9XAoog+JAlVC45tSo0nFeh7vNw9nBQr1+QRiysWTgy91kMH45BHDjruH VPxY7HikN4Dtoiisw9KwHmtzr9UPFQZiPe8dNwY7NqF9cSKUaQ3sFeRCJokxfALr sbHmrrVcS3h8wTWlc7QvNUlrkX+f/U9pJUD0JcEyhULnMGsHMj0N7YMkgAziSoQM bSFzu4Mk0E67Kr7BpX0rUmOfc4LrTOyExOQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvddufedggedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnth gvrhhprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeehleffgeegudejteei hfelteduvdeifffhffdvjedvffegjeekudeludehudeifeenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghu thesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Feedback-ID: i131946ab:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 8 Mar 2023 11:23:49 -0500 (EST) Message-ID: Date: Wed, 8 Mar 2023 17:23:48 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: Add documentation for coverage reports with meson Content-Language: en-US To: Michael Paquier Cc: Postgres hackers References: From: Peter Eisentraut In-Reply-To: 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 03.03.23 12:12, Michael Paquier wrote: > + > +meson setup -Db_coverage=true ... OTHER OPTIONS ... builddir/ > +cd builddir/ > +meson compile > +meson test > +ninja coverage-html > + The "cd" command needs to be moved after the meson commands, and the meson commands need to have a -C builddir option. So it should be like meson setup -Db_coverage=true ... OTHER OPTIONS ... builddir/ meson compile -C builddir meson test -C builddir cd builddir/ ninja coverage-html Otherwise, this looks good to me.