Re: Coverage (lcov) failing with inconsistent error in versions 2.x

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: "Jonathan Gonzalez V(dot)" <jonathan(dot)abdiel(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Coverage (lcov) failing with inconsistent error in versions 2.x
Date: 2026-07-01 12:28:44
Message-ID: CAOYmi+mT_=uC-kq_r_pifHWF5m2oqaDtXGTG47GpPQNhLSvyFQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 1, 2026 at 5:14 AM Jonathan Gonzalez V.
<jonathan(dot)abdiel(at)gmail(dot)com> wrote:
> These failure has already been discussed here[0], but this is a
> patch on the code rather than add an exception.

Thanks for the patch!

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ewan Young 2026-07-01 12:32:05 Re: Fix jsonpath .decimal() to honor silent mode
Previous Message Tatsuo Ishii 2026-07-01 12:18:05 Re: Row pattern recognition