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

From Alvaro Herrera
Subject Re: Bogus reports from coverage.postgresql.org
Date
Msg-id 20190530191130.GA24528@alvherre.pgsql
Whole thread Raw
In response to Re: Bogus reports from coverage.postgresql.org  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-www
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



pgsql-www by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: CF wishlist / where to discuss that
Next
From: Alvaro Herrera
Date:
Subject: Re: Bogus reports from coverage.postgresql.org