Re: Bogus reports from coverage.postgresql.org - Mailing list pgsql-www

From Tom Lane
Subject Re: Bogus reports from coverage.postgresql.org
Date
Msg-id 30195.1520790475@sss.pgh.pa.us
Whole thread Raw
In response to Re: Bogus reports from coverage.postgresql.org  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Bogus reports from coverage.postgresql.org
List pgsql-www
Magnus Hagander <magnus@hagander.net> writes:
> On Sun, Mar 11, 2018 at 3:08 PM, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote:
>> On 3/9/18 19:36, Tom Lane wrote:
>>> I happened to notice that if you look at
>>> https://coverage.postgresql.org/src/backend/optimizer/util/predtest.c.gcov.html
>>> it claims that the two occurrences of
>>> elog(ERROR, "predicate_classify returned a bogus value");
>>> at lines 492 and 803 are reached.

>> I can't reproduce this locally, so yeah, maybe we should check whether
>> the toolchain could be updated.

Now that I look, I don't see this behavior on my local machine (RHEL6,
gcc 4.4.7, lcov 1.10) either.

> Is it specifically "lcov" we are considering here? If so, we are on version
> 1.13, and there is no newer version packaged for debian or from what I can
> tell even released?

It could also be a compiler issue, I believe.

            regards, tom lane


pgsql-www by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Bogus reports from coverage.postgresql.org
Next
From: Tom Lane
Date:
Subject: Re: Bogus reports from coverage.postgresql.org