Re: Differential Code Coverage report for Postgres

From: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
To: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Subject: Re: Differential Code Coverage report for Postgres
Date: 2025-09-05 16:23:31
Message-ID: CAN55FZ1gbGWjSDAaNv=+T=gAMWhiZw9wYFH2GfKr6ZY33Y_6hA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Fri, 5 Sept 2025 at 18:14, Jacob Champion
<jacob(dot)champion(at)enterprisedb(dot)com> wrote:
>
> On Fri, Sep 5, 2025 at 12:09 AM Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> 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.
>
> This is fantastic timing! Differential coverage will be incredibly
> useful to have for some upcoming test patches I am writing. :) I will
> take a look.

I hope it helps! I updated the README on the repository to show how
you can run it on your local.

--
Regards,
Nazir Bilal Yavuz
Microsoft

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2025-09-05 16:27:14 Re: [PATCH] Let's get rid of the freelist and the buffer_strategy_lock
Previous Message Nazir Bilal Yavuz 2025-09-05 16:22:30 Re: Differential Code Coverage report for Postgres