pg.ddx.io  pgsql-www@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: PostgreSQL WWW <pgsql-www@lists.postgresql.org>
Subject: Re: Bogus reports from coverage.postgresql.org
Date: Wed, 14 Mar 2018 12:43:52 -0300
Message-ID: <20180314154352.ao4psdohgxd4pw65@alvherre.pgsql> (raw)
In-Reply-To: <27631.1521041578@sss.pgh.pa.us>

Tom Lane wrote:
> Peter Eisentraut <peter.eisentraut@2ndquadrant.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




view thread (44+ messages)  latest in thread

Message-ID: <20180314154352.ao4psdohgxd4pw65@alvherre.pgsql>
Permalink:  ../20180314154352.ao4psdohgxd4pw65@alvherre.pgsql/
Also on:    postgresql.org/message-id/20180314154352.ao4psdohgxd4pw65@alvherre.pgsql

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-www@postgresql.org
  Cc: alvherre@alvh.no-ip.org, tgl@sss.pgh.pa.us, peter.eisentraut@2ndquadrant.com, sfrost@snowman.net, magnus@hagander.net, pgsql-www@lists.postgresql.org
  Subject: Re: Bogus reports from coverage.postgresql.org
  In-Reply-To: <20180314154352.ao4psdohgxd4pw65@alvherre.pgsql>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox