| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Subject: | Re: Differential Code Coverage report for Postgres |
| Date: | 2025-09-05 15:14:14 |
| Message-ID: | sh4mpv2xzluu5pyl6rkzndjtbm6fpi77aps6iuxadkulv7cx2q@nsnxe2cwy53e |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2025-09-05 15:51:07 | Re: plan shape work |
| Previous Message | Jacob Champion | 2025-09-05 15:14:06 | Re: Differential Code Coverage report for Postgres |