From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-www@lists.postgresql.org
Subject: Bogus reports from coverage.postgresql.org
Date: Fri, 09 Mar 2018 19:36:28 -0500
Message-ID: <30022.1520642188@sss.pgh.pa.us> (raw)
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.
This would be quite astonishing if true, but it isn't true, since
the regression tests aren't reporting any such failure.
Needless to say, this puts quite a damper on my faith in the coverage
reports. Maybe that machine needs a software update?
regards, tom lane
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: tgl@sss.pgh.pa.us, pgsql-www@lists.postgresql.org
Subject: Re: Bogus reports from coverage.postgresql.org
In-Reply-To: <30022.1520642188@sss.pgh.pa.us>
* 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