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 1evqZZ-000537-Se for pgsql-www@arkaria.postgresql.org; Tue, 13 Mar 2018 20:31:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1evqZY-00057C-RX for pgsql-www@arkaria.postgresql.org; Tue, 13 Mar 2018 20:31:00 +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 1evqZY-000573-J4 for pgsql-www@lists.postgresql.org; Tue, 13 Mar 2018 20:31:00 +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 1evqZV-000237-NU for pgsql-www@lists.postgresql.org; Tue, 13 Mar 2018 20:30:59 +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 w2DKUpoc000964; Tue, 13 Mar 2018 16:30:51 -0400 From: Tom Lane To: Stephen Frost cc: Peter Eisentraut , Magnus Hagander , PostgreSQL WWW Subject: Re: Bogus reports from coverage.postgresql.org In-reply-to: <20180313170105.GC2416@tamriel.snowman.net> References: <30195.1520790475@sss.pgh.pa.us> <30669.1520791101@sss.pgh.pa.us> <31446.1520791925@sss.pgh.pa.us> <1594.1520795000@sss.pgh.pa.us> <2633.1520796277@sss.pgh.pa.us> <13148.1520798486@sss.pgh.pa.us> <20180313170105.GC2416@tamriel.snowman.net> Comments: In-reply-to Stephen Frost message dated "Tue, 13 Mar 2018 13:01:05 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <962.1520973051.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Tue, 13 Mar 2018 16:30:51 -0400 Message-ID: <963.1520973051@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Stephen Frost writes: > Which seems to indicate that this actually is some kind of lcov bug. > That makes more sense too since lcov is 1.13 on coverage.p.o, but you > used 1.10 and said you didn't see an issue. Not sure if you have access > to 1.13 easily, but if so, could be useful to see if you're seeing the > same behavior under 1.13 where the gcov output is correct but lcov > output isn't. Hpmh. So I tested Fedora 26, which has lcov 1.12, and that seems fine. Then I installed pre-release Fedora 28, which has lcov 1.13, and that does not work at all: $ make coverage-html = /usr/bin/lcov --gcov-tool /usr/bin/gcov -q --no-external -c -i -d . -d . -= o lcov_base.info geninfo: WARNING: /home/tgl/pgsql/src/backend/catalog/aclchk.gcno: Overlon= g record at end of file! geninfo: WARNING: /home/tgl/pgsql/src/backend/catalog/pg_subscription.gcno= : Overlong record at end of file! geninfo: WARNING: /home/tgl/pgsql/src/backend/catalog/pg_db_role_setting.g= cno: Overlong record at end of file! ... lots more ... geninfo: WARNING: /home/tgl/pgsql/src/backend/storage/lmgr/predicate.gcno:= Overlong record at end of file! geninfo: ERROR: /home/tgl/pgsql/src/backend/storage/lmgr/lwlocknames.gcno:= reached unexpected end of file make: *** [src/Makefile.global:911: lcov_base.info] Error 255 make: *** Deleting file 'lcov_base.info' Eyeing the commit history at https://github.com/linux-test-project/lcov/commits/master makes it appear that lcov doesn't work with gcc 8.0 yet (well, they committed support last week, but there's no release yet). So this is basically Fedora breakage ... but it means I don't have an easy way to check 1.13 except by installing handmade packages, which would probably not be definitive proof one way or the other. regards, tom lane