Re: Having problems generating a code coverage report

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