Re: Having problems generating a code coverage report
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Aleksander Alekseev <aleksander@timescale.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-01-29T01:00:38Z
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