Re: Having problems generating a code coverage report
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Aleksander Alekseev <aleksander@timescale.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-01-15T21:44:10Z
Lists: pgsql-hackers
Peter Geoghegan <pg@bowt.ie> writes: > On Wed, Oct 30, 2024 at 5:26 PM Peter Geoghegan <pg@bowt.ie> wrote: >> I've also been unable to generate coverage reports for some time (at >> least on Debian, with LCOV version 2.0-1). > I found a temporary workaround. I'm now once again able to produce > html coverage reports on my Debian unstable workstation. I got around to poking at this on a shiny new Fedora 41 image, with gcc-14.2.1 and lcov-2.0-4. I see errors and warnings aplenty there too, but after reading the suppression hints that appear in the error messages I was able to make them all go away: $ make -s coverage-html GENHTML_FLAGS="-q --legend --ignore-errors unmapped,unmapped" Overall coverage rate: lines......: 60.7% (282865 of 466310 lines) functions......: 67.4% (16114 of 23895 functions) $ The "-q --legend" part is our default value of GENHTML_FLAGS, the new magic is the --ignore-errors bit. As far as I can tell, specifying "unmapped" once reduces that class of errors to warnings and specifying it again silences them entirely. With this, I got plausible-looking html output (I didn't vet it in detail, but a couple of spot checks looked sane). I'm curious whether a similar workaround will help with the Debian toolchain. regards, tom lane