From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jacob Champion <jacob.champion@enterprisedb.com>
Cc: Jonathan Gonzalez V. <jonathan.abdiel@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Coverage (lcov) failing with inconsistent error in versions 2.x
Date: Wed, 01 Jul 2026 11:55:48 -0400
Message-ID: <3422076.1782921348@sss.pgh.pa.us> (raw)
In-Reply-To: <CAOYmi+kw+LL82qjiBmwrigk85fKcBn++UtVKAEcDRRWn3ZXy=Q@mail.gmail.com>
References: <87ldbuc3ik.fsf@gmail.com>
<CAOYmi+mT_=uC-kq_r_pifHWF5m2oqaDtXGTG47GpPQNhLSvyFQ@mail.gmail.com>
<874iiibxui.fsf@gmail.com>
<CAOYmi+kw+LL82qjiBmwrigk85fKcBn++UtVKAEcDRRWn3ZXy=Q@mail.gmail.com>
Jacob Champion <jacob.champion@enterprisedb.com> writes:
> (As an aside: I want to be careful in how I speak about lcov 2.x. I'm
> not an expert in that system, and it's entirely possible that all of
> the errors causing it to bail out by default are in fact legitimate
> problems in the underlying coverage data that is emitted by a
> compiler, rather than bugs in lcov. But I do believe that the current
> state of lcov makes it pretty much unfit for purpose with today's
> widely-used toolchains and codebases. I'm pretty disappointed in how
> v2 is behaving.)
Yeah. It seems like lcov 2.0 is kind of okay (it's working for me
anyway), but the later versions are more broken. I'm not excited
about changing our docs to reflect that, and definitely -1 on
changing our code. I think we just have to wait and hope they
get things sorted.
> We could rewrite https://wiki.postgresql.org/wiki/CodeCoverage, maybe.
+1, that page seems to be mostly ancient history at present.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, jacob.champion@enterprisedb.com, jonathan.abdiel@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: Coverage (lcov) failing with inconsistent error in versions 2.x
In-Reply-To: <3422076.1782921348@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox