| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL WWW <pgsql-www(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Bogus reports from coverage.postgresql.org |
| Date: | 2019-05-30 19:16:50 |
| Message-ID: | 20190530191650.GA24909@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On 2019-May-30, Alvaro Herrera wrote:
> 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?
I think I found the answer in this commit:
https://github.com/ccache/ccache/commit/02d3f078bd2495b8db2264ae0b2c692b4c5ba1bd
"Add support for coverage (compiling for gcov)"
committed for ccache 3.2.2.
So I think we could remove that stuff now ...
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nasby, Jim | 2019-05-31 14:18:18 | Wiki editor request |
| Previous Message | Alvaro Herrera | 2019-05-30 19:11:30 | Re: Bogus reports from coverage.postgresql.org |