pg.ddx.io  pgsql-www@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@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: Tue, 17 Sep 2019 22:15:02 +0200
Message-ID: <5d1b8859-3bca-9d98-31b7-e43a302446ec@2ndquadrant.com> (raw)
In-Reply-To: <10512.1568751170@sss.pgh.pa.us>
References: <20190530191650.GA24909@alvherre.pgsql>
	<82447.1559409033@sss.pgh.pa.us>
	<854d3409-87d0-fa44-430d-ce2babc58f1d@2ndquadrant.com>
	<10512.1568751170@sss.pgh.pa.us>

On 2019-09-17 22:12, Tom Lane wrote:
> Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
>> On 2019-06-01 19:10, Tom Lane wrote:
>>> 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?
> 
>> I happened to come across this again.  I think we should make the change
>> Álvaro was proposing.  The fix in ccache is 5 years old now.
> 
> Fair enough, I can just install a newer ccache version locally.
> 
> But should we worry about any buildfarm members running old ccache
> versions?  It'd probably be polite to notify the owners list about
> what the minimum ccache version is going to be.

Buildfarm members are not running coverage, are they?

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services





view thread (44+ messages)  latest in thread

Message-ID: <5d1b8859-3bca-9d98-31b7-e43a302446ec@2ndquadrant.com>
Permalink:  ../5d1b8859-3bca-9d98-31b7-e43a302446ec@2ndquadrant.com/
Also on:    postgresql.org/message-id/5d1b8859-3bca-9d98-31b7-e43a302446ec@2ndquadrant.com

 · 

reply

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: peter.eisentraut@2ndquadrant.com, tgl@sss.pgh.pa.us, alvherre@2ndquadrant.com, magnus@hagander.net, pgsql-www@lists.postgresql.org
  Subject: Re: Bogus reports from coverage.postgresql.org
  In-Reply-To: <5d1b8859-3bca-9d98-31b7-e43a302446ec@2ndquadrant.com>

* 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