Re: Having problems generating a code coverage report - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Having problems generating a code coverage report
Date
Msg-id aZJ3mpqZ-jECaZ9r@paquier.xyz
Whole thread Raw
In response to Re: Having problems generating a code coverage report  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
Responses Re: Having problems generating a code coverage report
List pgsql-hackers
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

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: pgsql: postgres_fdw: Inherit the local transaction's access/deferrable
Next
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: BUG: Former primary node might stuck when started as a standby