| From: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Subject: | Differential Code Coverage report for Postgres |
| Date: | 2025-09-05 07:09:27 |
| Message-ID: | CAN55FZ2k0sJpr0GxWW2-hsERx=YKciAAPVBPc_cTRa4NfkU9sg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
I also set up a GitHub Action so the report is updated daily and
published as HTML here [2].
I thought this might be useful to share, and I would be happy to hear
any feedback or suggestions.
CC’ing Álvaro since he had asked about this previously.
[1] https://github.com/nbyavuz/postgres-code-coverage/blob/main/code_coverage.sh
[2] https://nbyavuz.github.io/postgres-code-coverage
--
Regards,
Nazir Bilal Yavuz
Microsoft
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Sharma | 2025-09-05 07:19:55 | Re: How can end users know the cause of LR slot sync delays? |
| Previous Message | Michael Paquier | 2025-09-05 06:35:21 | Re: pg_upgrade: transfer pg_largeobject_metadata's files when possible |