public inbox for [email protected]
help / color / mirror / Atom feedFrom: Michael Paquier <[email protected]>
To: Andres Freund <[email protected]>
Cc: Aleksander Alekseev <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Cc: jian he <[email protected]>
Cc: Peter Geoghegan <[email protected]>
Subject: Re: Having problems generating a code coverage report
Date: Thu, 22 Jan 2026 09:48:35 +0900
Message-ID: <[email protected]> (raw)
In-Reply-To: <nqql77bmqixd232hrb6paw47evj6ramp6omsatwoofuzflcwak@j6t2wru3iqfd>
References: <CAJ7c6TN+MCh99EZ8YGhXZAdnqvNQYir6E34B_mmcB5KsxCB00A@mail.gmail.com>
<CAH2-WzkTDv1PGhyssyHaV1smSEUNktDV3ACfwZsL-iE2=9hOVA@mail.gmail.com>
<[email protected]>
<CAJ7c6TPYPF93+yWi=ThKiOsnhqLpeTmctMrJWz3xRQobGSY6BA@mail.gmail.com>
<CACJufxG+vX_pfPNJTo1WXP_QzGO1KXrVa0yYMkpBqL8nJvQ-VA@mail.gmail.com>
<CAJ7c6TMhH2DK6uAGekrn5Xbd5PcPMkTfN4Ot2EfBkuRB3QVy7g@mail.gmail.com>
<CAJ7c6TNg-4Lc4rXkM3SA95LCUef5QPvfiTAOAe58=8g6oenzuw@mail.gmail.com>
<CAJ7c6TOkAMyHuNPWnF5S9ciOtB52reNgcv50XtyQNb2gY_DYyA@mail.gmail.com>
<nqql77bmqixd232hrb6paw47evj6ramp6omsatwoofuzflcwak@j6t2wru3iqfd>
On Wed, Jan 21, 2026 at 01:57:58PM -0500, Andres Freund wrote:
> I just encountered this. The problem seems to only happen when the build
> directory is inside the source directory.
>
> Not that that's a great solution, but just having the build dir be in a
> separate directory fixed the issue for me.
Even with a VPATH build on Debien GID? FWIW, I am unable to run a
coverage-html even in this case from the root of a build, finishing
with stuff like that:
/usr/bin/lcov --gcov-tool /usr/bin/gcov -q --no-external -c -i -d . -d
/home/user/git/postgres/ -o lcov_base.info
lcov: ERROR: (empty) no .gcno files found in /home/user/git/postgres
(use "lcov --ignore-errors empty ..." to bypass this error)
Passing "--ignore-errors empty" to LCOVFLAGS bypasses the first step
but genhtml complains, like:
genhtml: ERROR: (corrupt) unable to read trace file 'lcov_base.info':
meson is no better as far as I've tried, so I have pretty much given
up with coverage reports in this environment at this stage. If there
is a magic recipe, I am not really aware of one..
--
Michael
Attachments:
[application/pgp-signature] signature.asc (833B, ../[email protected]/2-signature.asc)
download
view thread (12+ 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