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

From Andres Freund
Subject Re: Differential Code Coverage report for Postgres
Date
Msg-id sh4mpv2xzluu5pyl6rkzndjtbm6fpi77aps6iuxadkulv7cx2q@nsnxe2cwy53e
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
Hi,

On 2025-09-05 10:09:27 +0300, Nazir Bilal Yavuz wrote:
> 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.

I wonder if it'd be better to compare the merge base between master and
REL_18_STABLE, rather than REL_18_STABLE [1].


> I also set up a GitHub Action so the report is updated daily and
> published as HTML here [2].

Nice!

How hard would it be to compare not just REL_18_STABLE and master, but also
REL_17_STABLE and REL_18_STABLE?

Greetings,

Andres Freund

[1] git merge-base master REL_18_STABLE



pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: Differential Code Coverage report for Postgres
Next
From: Robert Haas
Date:
Subject: Re: plan shape work