From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: PostgreSQL WWW <pgsql-www@lists.postgresql.org>
Subject: Re: Bogus reports from coverage.postgresql.org
Date: Sat, 01 Jun 2019 13:10:33 -0400
Message-ID: <82447.1559409033@sss.pgh.pa.us> (raw)
In-Reply-To: <20190530191650.GA24909@alvherre.pgsql>
References: <20190530191650.GA24909@alvherre.pgsql>
Alvaro Herrera <alvherre@2ndquadrant.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-www@postgresql.org
Cc: tgl@sss.pgh.pa.us, alvherre@2ndquadrant.com, peter.eisentraut@2ndquadrant.com, magnus@hagander.net, pgsql-www@lists.postgresql.org
Subject: Re: Bogus reports from coverage.postgresql.org
In-Reply-To: <82447.1559409033@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox