From: "Jonathan Gonzalez V." <jonathan.abdiel@gmail.com>
To: =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de>
Cc: Jacob Champion <jacob.champion@enterprisedb.com>,
  pgsql-hackers@lists.postgresql.org
Subject: Re: Coverage (lcov) failing with inconsistent error in versions 2.x
In-Reply-To: <akvo_IGW-iP2n579@alvherre.pgsql> (=?utf-8?Q?=22=C3=81lvaro?=
 Herrera"'s message of
	"Mon, 6 Jul 2026 20:00:34 +0200")
References: <akvo_IGW-iP2n579@alvherre.pgsql>
Date: Tue, 14 Jul 2026 13:06:17 +0200
Message-ID: <87v7ahq192.fsf@gmail.com>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/87v7ahq192.fsf%40gmail.com>
Precedence: bulk


Hello!

=C3=81lvaro Herrera <alvherre@kurilemu.de> writes:

> On 2026-Jul-06, Jacob Champion wrote:
>
>> On Fri, Jul 3, 2026 at 1:17=E2=80=AFPM =C3=81lvaro Herrera <alvherre@kur=
ilemu.de> wrote:
>> > I added -j0 to both so that they run parallel processes, which should =
be
>> > a few second faster.
>>=20
>> As a heads up, I found that adding parallelism on my local machine ran
>> it out of memory pretty quickly, with lcov 2.4. YMMV.
>
> Strange!
>
> Anyway I noticed that "-j0" doesn't work -- apparently it has to be "-j 0=
".
> I'll see how bad the memory usage gets on the next report, and turn that
> off (or set it lower?) if things are too tight.

I ran into the same issues and I took a different direction, since lcov
wasn't working I started to look for other solutions, turns out that
meson comes with a fallback if lcov is not installed called gcovr, and
works really well, at least for my requirements (not running in the full
stack), without any configuration I have a coverage report, enough at
least.

Has anyone tried gcovr before? I'd be interested to know whether there
are any drawbacks to using it.

Going back to lcov, according to an issue [0], it looks like users are
expected to use the "TOT" version, which makes no sense to me. I tested
the latest lcov release from last week, and I'm still experiencing the
same issues that started this thread.

In conclusion, I'll stick with gcovr for now rather than maintaining an
lcov configuration with many exceptions.

[0] https://github.com/linux-test-project/lcov/issues/473#issuecomment-4492=
099808

Regards

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