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 aZVaYX8_nwdLCadZ@paquier.xyz
Whole thread Raw
In response to Re: Having problems generating a code coverage report  (Álvaro Herrera <alvherre@kurilemu.de>)
List pgsql-hackers
On Tue, Feb 17, 2026 at 06:28:24PM +0100, Alvaro Herrera wrote:
> Correction.  These variables are not taken into account if given as
> environment variables, but they are if given as make arguments.
> Moreover, --legend makes lcov die.  So, apparently this one works:
>
> make coverage-html LCOVFLAGS="-q --ignore-errors usage" GENHTML_FLAGS="-q --legend --ignore-errors
unmapped,corrupt,inconsistent,range"
>
> I also removed a file called .lcovrc that only had this line
>   lcov_branch_coverage = 0
> though that doesn't appear to have automatically added branch coverage
> to the report.  However, I'll wait until the next run to see if anything
> changes.

Based on your ideas, I have been able to get my way through today with
this modified artistic flavor, for a non-VPATH build, in a Fedora
environment:
make coverage-html \
    LCOVFLAGS="-q --ignore-errors gcov,gcov" \
    GENHTML_FLAGS="-q --legend --ignore-errors unmapped,corrupt,unmapped,inconsistent"
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Shinya Kato
Date:
Subject: Re: Avoid recalculating pgprocno in ProcArrayAdd()
Next
From: Amit Kapila
Date:
Subject: Re: Skipping schema changes in publication