Re: Differential Code Coverage report for Postgres - Mailing list pgsql-hackers

From Álvaro Herrera
Subject Re: Differential Code Coverage report for Postgres
Date
Msg-id 202510061258.qvc2d7l6lfhs@alvherre.pgsql
Whole thread Raw
In response to Differential Code Coverage report for Postgres  (Nazir Bilal Yavuz <byavuz81@gmail.com>)
Responses Re: Differential Code Coverage report for Postgres
List pgsql-hackers
On 2025-Sep-05, Nazir Bilal Yavuz wrote:

> Hi,
> 
> I have been working on generating differential code coverage for
> Postgres and was able to do so with this script [1]. The script checks
> out HEAD and the latest release branch (currently REL_18_STABLE), then
> generates a differential coverage report.

Why does it need llvm-16-dev in addition to llvm-dev?  In current
debian, the latter is llvm-14-dev, but I suppose that should just as
well for lcov, or does it not work?

Also, I'm curious on why it installs a bunch of mingw32 packages ... is
that a leftover from making it produce results for mingw32 also, or is
it actually needed for the current script?  (I don't see any usage of
that elsewhere in the script, hence the question).  I see a bunch of
other unrelated things, such as docbook, fop etc (ultimately installing
the full java toolchain) ...

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/
"Puedes vivir sólo una vez, pero si lo haces bien, una vez es suficiente"



pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: Changing the state of data checksums in a running cluster
Next
From: Chao Li
Date:
Subject: Re: src/include/utils/float.h comment one link stable