Re: Having problems generating a code coverage report - Mailing list pgsql-hackers

From jian he
Subject Re: Having problems generating a code coverage report
Date
Msg-id CACJufxG+vX_pfPNJTo1WXP_QzGO1KXrVa0yYMkpBqL8nJvQ-VA@mail.gmail.com
Whole thread Raw
In response to Re: Having problems generating a code coverage report  (Aleksander Alekseev <aleksander@timescale.com>)
Responses Re: Having problems generating a code coverage report
List pgsql-hackers
On Thu, Oct 31, 2024 at 10:02 PM Aleksander Alekseev
<aleksander@timescale.com> wrote:
>
> Hi,
>
> > On Wed, Oct 30, 2024 at 05:26:49PM -0400, Peter Geoghegan wrote:
> > > I use Debian unstable for most of my day to day work. Apparently
> > > Debian unstable has exactly the same version of lcov as Ubuntu 24.04.
> > >
> > > I've also been unable to generate coverage reports for some time (at
> > > least on Debian, with LCOV version 2.0-1).
> >
> > So do I, for both the debian SID and the lcov parts.
>
> I downgraded to lcov 1.16 [1] and it helped. This is merely a
> workaround of course, not a long-time solution.
>
> [1]: https://github.com/linux-test-project/lcov/releases/tag/v1.16
>
> --

my ubuntu meson version: 0.61.2, which also fails.
with similar errors you've posted.


from these two posts,
https://github.com/mesonbuild/meson/pull/12345
https://github.com/mesonbuild/meson/issues/11995

Maybe upgrading meson can solve this problem.



pgsql-hackers by date:

Previous
From: Stepan Neretin
Date:
Subject: Re: Making error message more user-friendly with spaces in a URI
Next
From: Bertrand Drouvot
Date:
Subject: Re: small pg_combinebackup improvements