| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, 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-06-01 17:10:33 |
| Message-ID: | 82447.1559409033@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> On 2019-May-30, Alvaro Herrera wrote:
>> On 2018-Mar-12, Peter Eisentraut wrote:
>>> --enable-coverage disables ccache, so that's not going to be it.
> 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 ...
I'd be a bit sad if we did, because where I usually do coverage checking
is my RHEL6 box, which has
$ ccache --version
ccache version 3.1.6
I'll probably bite the bullet and upgrade that box sometime in the
next year or so, but it's not really a near-term project. Is there
any big hurry for having ccache for coverage builds?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Phuangtan | 2019-06-02 05:41:07 | Wiki editor request |
| Previous Message | Nasby, Jim | 2019-05-31 18:53:59 | Maliing list request |