| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | "Jonathan Gonzalez V(dot)" <jonathan(dot)abdiel(at)gmail(dot)com> |
| Cc: | Álvaro Herrera <alvherre(at)kurilemu(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Coverage (lcov) failing with inconsistent error in versions 2.x |
| Date: | 2026-08-25 15:44:21 |
| Message-ID: | CAOYmi+=qnyhd+OeizEtb0mAm2H753p+NAire9no9BR-6Q1o05g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 14, 2026 at 4:06 AM Jonathan Gonzalez V.
<jonathan(dot)abdiel(at)gmail(dot)com> wrote:
> Has anyone tried gcovr before? I'd be interested to know whether there
> are any drawbacks to using it.
I recently tried meson+gcovr and wasn't very happy with the default
merging/filtering of the source and build trees. So I just copy-pasted
the gcovr invocation that meson does and tweaked it to work
correctly... annoying, but less annoying than lcov. (I still need lcov
for differential coverage, though, as far as I can tell.)
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2026-08-25 15:52:32 | Re: add list of major features to the v19 release notes |
| Previous Message | Jacob Champion | 2026-08-25 15:24:44 | Re: Changing client-side behavior regarding Certificate Revocation Lists (CRL) |