public inbox for [email protected]
help / color / mirror / Atom feedFrom: Michael Paquier <[email protected]>
To: Stefan Kaltenbrunner <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Aleksander Alekseev <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Cc: Peter Geoghegan <[email protected]>
Subject: Re: Having problems generating a code coverage report
Date: Mon, 16 Feb 2026 10:49:14 +0900
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CAJ7c6TN+MCh99EZ8YGhXZAdnqvNQYir6E34B_mmcB5KsxCB00A@mail.gmail.com>
<CAH2-WzkTDv1PGhyssyHaV1smSEUNktDV3ACfwZsL-iE2=9hOVA@mail.gmail.com>
<CAH2-WzmemwQFQBbzuZs5UUb-JDBo2A7R-aBt_Hc=A6ZnKXyycQ@mail.gmail.com>
<[email protected]>
<CAH2-Wz=bc9VdC5yxXnLcTm6CVsoNH1Qxd_JgcFbCPRGqAdY_Ag@mail.gmail.com>
<[email protected]>
<[email protected]>
On Sat, Feb 14, 2026 at 09:04:44AM +0100, Stefan Kaltenbrunner wrote:
> While I certainly can try to locally hack around that further to get it
> build it feels wrong to post process/patch our own tree to get "official"
> coverage reporting...
Are you using a VPATH build? That was the only build option that was
causing me problems on Debian GID even with the tweaks proposed by
Andres in a .lcovrc. Non-vpath under configure and meson worked
unpatched. With vpath under configure, that worked but the
directories were in a weird state (contrib/ missing from the root
patch, $HOME included). meson was much slower than the two others.
I have also tried a few more experiments on Fedora 34 lately, that
points to even newer versions of all these tools. Things are even
more broken moving forward for meson, vpath and non-vpath. This is
testing things with an unpatched PG tree, just mentioning that it
does not seem to get better as time goes..
--
Michael
Attachments:
[application/pgp-signature] signature.asc (833B, ../[email protected]/2-signature.asc)
download
view thread (4+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Having problems generating a code coverage report
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox