Re: Differential Code Coverage report for Postgres

Hi,

On Mon, 6 Oct 2025 at 16:02, Álvaro Herrera <alvherre@kurilemu.de> wrote:
>
> 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) ...

Sorry for the confusion. We have a script that installs linux
dependencies for the CI [1]. I just copied the contents of this script
to make sure that I don't miss any dependencies, probably these
dependencies are much larger than we actually need.

[1] https://github.com/anarazel/pg-vm-images/blob/main/scripts/linux_debian_install_deps.sh

--
Regards,
Nazir Bilal Yavuz
Microsoft