| From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
|---|---|
| To: | Narek Galstyan <narek(dot)galstyan(at)enterprisedb(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, "narekg(at)berkeley(dot)edu" <narekg(at)berkeley(dot)edu>, ngalstyan4(at)gmail(dot)com |
| Subject: | Re: Coverage with make coverage-html is broken on latest Debian using lcov v2 |
| Date: | 2026-06-15 18:22:45 |
| Message-ID: | ajBA9Zuy3TZ73mxr@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Narek,
On 2026-Apr-21, Narek Galstyan wrote:
> On Debian 13 (trixie), `make coverage-html` command triggers an lcov
> failure.
[...]
> Without applying any of the patches, with --enable-coverage and in-tree
> build (no vpath), make check && make coverage-html results in the following
> error:
>
> ```
> /usr/bin/lcov --gcov-tool /usr/bin/gcov -q --no-external -c -i -d . -d . -o
> lcov_base.info
> lcov: ERROR: (usage) duplicate file ./src/backend/access/table/tableam.gcno
> in both . and .
Handling this part with your 0001 seems reasonable to me. I think we
should backpatch that one.
I'm not sure sure about the 0002 patch though. It builds in the
assumption that lcov is broken and that we're going to ignore these
warnings by default [forever]. Do we really want to bake those flags
into our build system?
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"El número de instalaciones de UNIX se ha elevado a 10,
y se espera que este número aumente" (UPM, 1972)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Jones | 2026-06-15 18:25:41 | Re: XMLDocument (SQL/XML X030) |
| Previous Message | Bharath Rupireddy | 2026-06-15 18:20:50 | Re: mxid_score can become Infinity in pg_stat_autovacuum_scores |