From: | Oreo Yang <oreo(dot)yang(at)hotmail(dot)com> |
---|---|
To: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, 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 10:39:28 |
Message-ID: | TY4P286MB7376DD8B50845AC54AA5DF35E703A@TY4P286MB7376.JPNP286.PROD.OUTLOOK.COM |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
It looks very cool.
So our goal over 90%?
Thanks,
OreoYang
________________________________
发件人: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
已发送: 2025 年 9 月 5 日 星期五 15:09
收件人: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
抄送: Andres Freund <andres(at)anarazel(dot)de>; Álvaro Herrera <alvherre(at)kurilemu(dot)de>
主题: Differential Code Coverage report for Postgres
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 | Matheus Alcantara | 2025-09-05 10:44:11 | Re: LISTEN/NOTIFY bug: VACUUM sets frozenxid past a xid in async queue |
Previous Message | Tatsuo Ishii | 2025-09-05 10:06:38 | Re: Raw parse tree is not dumped to log |