From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Having problems generating a code coverage report |
Date: | 2025-01-29 01:00:38 |
Message-ID: | Z5l9tg9rjc2xtZnQ@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jan 15, 2025 at 07:51:39PM -0500, Peter Geoghegan wrote:
> I was able to get the lcov git master branch's tip to produce a
> Postgres coverage report (same compiler version and OS as before).
> Unfortunately, I had to use an even grottier incantation to get this
> to work:
>
> make -s coverage-html GENHTML_FLAGS="-q --legend --ignore-errors
> unmapped,unmapped,empty,empty,inconsistent,inconsistent,corrupt,corrupt,range,range"
> LCOVFLAGS="--ignore-errors
> empty,empty,negative,negative,inconsistent,inconsistent"
>
> (As you can imagine, I came up with this through pure trial and error.)
Interesting. These tricks do not seem to work here with a Debian GID
host, unfortunately. I'll try to dig a bit more, this is getting very
annoying :(
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2025-01-29 01:20:56 | preptlist.c can insert unprocessed expression trees |
Previous Message | Peter Smith | 2025-01-29 00:32:34 | Re: Pgoutput not capturing the generated columns |