| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL WWW <pgsql-www(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Bogus reports from coverage.postgresql.org |
| Date: | 2018-03-12 15:06:19 |
| Message-ID: | CABUevEzfdNCCdKu1sZ0Z+i6RKo07JwCazhR_dGfSH-CoEp0q5g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Mon, Mar 12, 2018 at 3:53 PM, Peter Eisentraut <
peter(dot)eisentraut(at)2ndquadrant(dot)com> 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.
>
>
That certainly makes that coding put into the script (which has been there
for a long time) completely wrong :)
That said, it completed with that row commented out, and AFAICT the issue
is still lthere :( So much for that theory.
--
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 | Mark Wong | 2018-03-12 17:11:27 | Re: planning for perf farm app |
| Previous Message | Peter Eisentraut | 2018-03-12 14:53:34 | Re: Bogus reports from coverage.postgresql.org |