public inbox for [email protected]  

help / color / mirror / Atom feed

From: Álvaro Herrera <[email protected]>
To: Michael Paquier <[email protected]>
Cc: 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: Tue, 17 Feb 2026 18:28:24 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 2026-Feb-17, Álvaro Herrera wrote:

> Nope, it's a straight in-tree build.  I made it work after a few more
> failed tries with a call like
> 
> GENHTML_FLAGS="-q --legend --ignore-errors unmapped,corrupt,inconsistent,range"
> LCOVFLAGS="-q --legend --ignore-errors usage"
> make coverage-html

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.

The CSS problem appears to have been a caching glitch, and now it works,
so I guess the cached file must have expired.  It looks Christmas-treeish
again now.

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/
"No renuncies a nada. No te aferres a nada."

view thread (3+ 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], [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