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

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
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 18:00:34
Message-ID: akvo_IGW-iP2n579@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2026-Jul-06, Jacob Champion wrote:

> 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.

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.

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Pido que me den el Nobel por razones humanitarias" (Nicanor Parra)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tristan Partin 2026-07-06 18:10:27 Add returns_nonnull to infallible allocators
Previous Message Robert Haas 2026-07-06 17:50:46 Re: [RFC PATCH v0 0/7] Add EXPLAIN ANALYZE wait event reporting