Re: Bogus reports from coverage.postgresql.org

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL WWW <pgsql-www(at)lists(dot)postgresql(dot)org>
Subject: Re: Bogus reports from coverage.postgresql.org
Date: 2018-03-14 15:43:52
Message-ID: 20180314154352.ao4psdohgxd4pw65@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> > On 3/13/18 13:45, Tom Lane wrote:
> >> Yeah. I'd written that off as too low-probability to worry about,
> >> but maybe not. I'll poke further. Peter, which lcov did you test?
>
> > lcov: LCOV version 1.13
> > The one that comes with Debian stable, presumably the same that is
> > running on coverage.p.o.
>
> OK, now we're getting into the *really* low-probability cases. Like,
> maybe it's time to remove and reinstall lcov and/or gcc on that box?

I checked on my own Debian box, which shows

$ gcov --version
gcov (Debian 6.3.0-18+deb9u1) 6.3.0 20170516

$ lcov --version
lcov: LCOV version 1.13

and what I get is:
492 0 : elog(ERROR, "predicate_classify returned a bogus value");
803 0 : elog(ERROR, "predicate_classify returned a bogus value");

so.

In the coverage.pg.org box, we have:

$ cat .lcovrc
lcov_branch_coverage = 1

I'm going to do a test run with that disabled and see what happens.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Alvaro Herrera 2018-03-14 16:12:48 Re: Bogus reports from coverage.postgresql.org
Previous Message Tom Lane 2018-03-14 15:32:58 Re: Bogus reports from coverage.postgresql.org