Re: Bogus reports from coverage.postgresql.org

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL WWW <pgsql-www(at)lists(dot)postgresql(dot)org>
Subject: Re: Bogus reports from coverage.postgresql.org
Date: 2018-03-11 21:15:42
Message-ID: 19942.1520802942@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Sun, Mar 11, 2018 at 9:05 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> It might be worth blowing away ccache's cache just to see if it's cached
>> anything bogus.

> I've done that and completed a run. AFAICT it's still showing the same
> issue, right?

Yeah, looks like it to me. 'Tis a puzzlement.

regards, tom lane

In response to

Browse pgsql-www by date

  From Date Subject
Next Message Andrey Borodin 2018-03-12 06:47:48 Re: [HACKERS] GSoC 2017: weekly progress reports (week 6)
Previous Message Alexander Korotkov 2018-03-11 20:54:31 Re: [HACKERS] GSoC 2017: weekly progress reports (week 6)