From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: PostgreSQL WWW <pgsql-www@lists.postgresql.org>
Subject: Re: Bogus reports from coverage.postgresql.org
Date: Thu, 30 May 2019 15:11:30 -0400
Message-ID: <20190530191130.GA24528@alvherre.pgsql> (raw)
In-Reply-To: <82547845-0af5-fccf-81be-2119b3ce175b@2ndquadrant.com>
On 2018-Mar-12, Peter Eisentraut wrote:
> On 3/11/18 16:05, Tom Lane wrote:
> > It might be worth blowing away ccache's cache just to see if it's cached
> > anything bogus.
>
> --enable-coverage disables ccache, so that's not going to be it.
(Ref. src/Makefile.global.in lines 484ff setting CCACHE_DISABLE=1)
Why does it do that? Now that ccache is about 5 years less buggy than
it was when you wrote this, can we get rid of this behavior?
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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@2ndquadrant.com, peter.eisentraut@2ndquadrant.com, tgl@sss.pgh.pa.us, magnus@hagander.net, pgsql-www@lists.postgresql.org
Subject: Re: Bogus reports from coverage.postgresql.org
In-Reply-To: <20190530191130.GA24528@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