From: "Jonathan Gonzalez V." <jonathan.abdiel@gmail.com>
To: Jacob Champion <jacob.champion@enterprisedb.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Coverage (lcov) failing with inconsistent error in versions 2.x
In-Reply-To: 
 <CAOYmi+mT_=uC-kq_r_pifHWF5m2oqaDtXGTG47GpPQNhLSvyFQ@mail.gmail.com>
 (Jacob
	Champion's message of "Wed, 1 Jul 2026 05:28:44 -0700")
References: <87ldbuc3ik.fsf@gmail.com>
	<CAOYmi+mT_=uC-kq_r_pifHWF5m2oqaDtXGTG47GpPQNhLSvyFQ@mail.gmail.com>
Date: Wed, 01 Jul 2026 16:15:01 +0200
Message-ID: <874iiibxui.fsf@gmail.com>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: 
 <https://www.postgresql.org/message-id/874iiibxui.fsf%40gmail.com>
Precedence: bulk


Hi!

Jacob Champion <jacob.champion@enterprisedb.com> writes:
> Thanks for the patch!

Thanks for the quick answer!

> I'm not sure we should get on the treadmill of catering to lcov, when
> I look at the huge number of errors its 2.x line now throws for
> widely-used compilers and coding styles. (Right now my ignore_errors
> setting is up to six categories, I think. Which is unfortunate, but
> its signal-to-noise ratio is just not good right now. Just yesterday I
> had to patch out an error in 2.4 that was preventing me from running
> genhtml.)
>
> --Jacob

Right now with the version that I have for Ubuntu 26.04 (lcov 2.0) I
don't have more issues than the `range` one that I'm trying to confirm
in the other thread if it is or not an issue.

Well, if we're not tracking down all the errors, at least we should try
to keep some fix related to the code that make sense, and for other
errors, probably we should document which version of lcov we support and
the proper .lcovrc file with the errors to ignore so no one have the
same problem in the future?

I don't think anyone will want to add a .lcovrc file to the repository,
but probably a sample file in the documentation will work?

Thanks!
--
Jonathan Gonzalez V.
EDB
https://www.enterprisedb.com