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 20:05:30
Message-ID: 13354.1520798730@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:
> Hmm. So it works for you on exactly the same version that the server runs.
> That's interesting. Is there something wrong in how we run it? I wonder if
> its broken by ccache. What we have is:

It might be worth blowing away ccache's cache just to see if it's cached
anything bogus.

regards, tom lane

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Magnus Hagander 2018-03-11 20:32:56 Re: Bogus reports from coverage.postgresql.org
Previous Message Tom Lane 2018-03-11 20:01:26 Re: Bogus reports from coverage.postgresql.org