| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:32:56 |
| Message-ID: | CABUevEwghPKkCvdHpfvvHuLerf-nNF0VGXZNDxByax1-pCC-ow@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Sun, Mar 11, 2018 at 9:05 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.
>
I've done that and completed a run. AFAICT it's still showing the same
issue, right?
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2018-03-11 20:54:31 | Re: [HACKERS] GSoC 2017: weekly progress reports (week 6) |
| Previous Message | Tom Lane | 2018-03-11 20:05:30 | Re: Bogus reports from coverage.postgresql.org |