Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ew9YF-00036Q-5Z for pgsql-www@arkaria.postgresql.org; Wed, 14 Mar 2018 16:46:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ew9YD-0004th-Uq for pgsql-www@arkaria.postgresql.org; Wed, 14 Mar 2018 16:46:53 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ew9YD-0004tY-Mx for pgsql-www@lists.postgresql.org; Wed, 14 Mar 2018 16:46:53 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ew9YA-0003AC-NT for pgsql-www@lists.postgresql.org; Wed, 14 Mar 2018 16:46:52 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w2EGkdLC006736; Wed, 14 Mar 2018 12:46:40 -0400 From: Tom Lane To: Peter Eisentraut cc: Alvaro Herrera , Stephen Frost , Magnus Hagander , PostgreSQL WWW Subject: Re: Bogus reports from coverage.postgresql.org In-reply-to: <5744.1521045105@sss.pgh.pa.us> References: <20180314154352.ao4psdohgxd4pw65@alvherre.pgsql> <4710.1521044117@sss.pgh.pa.us> <5744.1521045105@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Wed, 14 Mar 2018 12:31:45 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <6734.1521045999.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 14 Mar 2018 12:46:39 -0400 Message-ID: <6735.1521045999@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk I wrote: > Our process swaps steps 1 and 2. What I now suspect is that > we accidentally get away with that for basic mode, but it > doesn't work with lcov_branch_coverage. I tested that theory by manually doing things in the "correct" order, and it didn't change the results: $ /usr/bin/lcov --gcov-tool /usr/bin/gcov -q --no-external -c -i -d . -d .= -o lcov_base.info geninfo: Note: --initial does not generate branch coverage data $ make check ... $ /usr/bin/lcov --gcov-tool /usr/bin/gcov -q --no-external -c -d . -d . -o= lcov_test.info $ rm -rf coverage $ /usr/bin/genhtml -q --legend -o coverage --title=3D'PostgreSQL 11devel' = --num-spaces=3D4 --prefix=3D'/home/tgl/pgsql' lcov_base.info lcov_test.inf= o $ grep bogus coverage/src/backend/optimizer/util/predtest.c.* coverage/src/backend/optimizer/util/predtest.c.gcov.html: 492 : 1018= 6 : elog(ERROR, "predicate_classify returned a bogus value")= ; coverage/src/backend/optimizer/util/predtest.c.gcov.html: 803 : 5948= 2 : elog(ERROR, "predicate_classify returned a bogus value")= ; I'm still a bit suspicious that we may have a process problem, but it's looking like there may be grounds for an lcov bug report. regards, tom lane