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

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: "Jonathan Gonzalez V(dot)" <jonathan(dot)abdiel(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Coverage (lcov) failing with inconsistent error in versions 2.x
Date: 2026-07-06 15:22:23
Message-ID: CAOYmi+n3xPigj2N=KQO_RXDNAGgrqSy=pX_yGBiBu_dz9zQOZg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jul 3, 2026 at 1:17 PM Álvaro Herrera <alvherre(at)kurilemu(dot)de> wrote:
> I added -j0 to both so that they run parallel processes, which should be
> a few second faster.

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.

Thanks!
--Jacob

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Matthias van de Meent 2026-07-06 15:44:50 Re: VACUUM FULL or CREATE INDEX fails with error: missing chunk number 0 for toast value XXX
Previous Message Ashutosh Bapat 2026-07-06 15:05:04 Re: Replace pg_atomic_flag with pg_atomic_bool