Re: Having problems generating a code coverage report
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Andres Freund <andres@anarazel.de>
Cc: Aleksander Alekseev <aleksander@timescale.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, jian he <jian.universality@gmail.com>, Peter Geoghegan <pg@bowt.ie>
Date: 2026-01-22T22:11:11Z
Lists: pgsql-hackers
On Thu, Jan 22, 2026 at 01:19:43PM -0500, Andres Freund wrote: > On 2026-01-22 14:35:40 +0900, Michael Paquier wrote: > If I suppress the empty errors & warnings with --ignore-errors empty,empty the > current "-d . -d $(srcdir)" kinda works. Unfortunately, in VPATH builds, the > directory structure is quite messed up. It seems to get a bit better if I add > -p $(srcdir) to the genhtml invocation, but a few generated files still show > up bogus. With a bit more information to skip more error patterns, I actually got an unpatched HEAD build able to work properly as well, with: ignore_errors=inconsistent,gcov,range,empty,usage,usage,empty,empty,path The VPATH build is indeed looking pretty broken here, with the top-level including the contents of src/ and /home/, /home/ pointing to contrib/. I'll live with that, that's so much better than nothing working locally. Thanks for all the pointers, Andres. -- Michael