On 2026-Feb-16, Michael Paquier wrote:
> On Sat, Feb 14, 2026 at 09:04:44AM +0100, Stefan Kaltenbrunner wrote:
> > While I certainly can try to locally hack around that further to get it
> > build it feels wrong to post process/patch our own tree to get "official"
> > coverage reporting...
>
> Are you using a VPATH build?
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
... and we have a nice (??) trace of what errors are being ignored. I
think this is absolutely bonkers, but who knows when or if lcov and its
tools are going to be fixed in a way that allows our tree to be
processed correctly.
However, it appears that there are problems with the CSS, because the
lines are not colored anymore. I have no idea how to get this to work,
but you can see the result running lcov 2.0 in
https://coverage.postgresql.org/
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"You're _really_ hosed if the person doing the hiring doesn't understand
relational systems: you end up with a whole raft of programmers, none of
whom has had a Date with the clue stick." (Andrew Sullivan)
https://postgr.es/m/20050809113420.GD2768@phlogiston.dyndns.org
