public inbox for [email protected]  

help / color / mirror / Atom feed

From: David Steele <[email protected]>
To: Andrew Dunstan <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: Michael Paquier <[email protected]>
Cc: Postgres hackers <[email protected]>
Subject: Re: Re: Rewriting the test of pg_upgrade as a TAP test - take two
Date: Wed, 21 Mar 2018 10:51:04 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<CAA8=A79KwJ4Yt3C9LAMt9-i+N=jDP2Z+NoE0qh069BetX0kmCw@mail.gmail.com>
	<CAA8=A7-xR98DkqdoTAui3i4Y17xJPrMrxYGr9KDh0Hs0qVYjMg@mail.gmail.com>
	<[email protected]>
	<[email protected]>

On 3/6/18 4:12 PM, Tom Lane wrote:
> Peter Eisentraut <[email protected]> writes:
>> On 3/4/18 16:09, Andrew Dunstan wrote:
>>> If you want to do this soon I can put out a Buildfarm Client release
>>> fairly quickly.
> 
>> I think the dependency is mostly the other way around.  How quickly
>> would build farm owners install the upgrade?
> 
> IIUC, the buildfarm script patch is only needed to avoid duplicate
> tests.  So owners need only install it if they want to reduce wasted
> cycles on their machines.  That being the case, it's only urgent to
> the extent that the individual owner perceives it to be.  Some might
> think it is so, so I'd like to see the BF release available before
> we push the TAP test ... but we don't have to wait very long between.

It seems the consensus is that we'll need a build farm update before we
can move forward with the patch and that we don't need to wait long for
people to upgrade.

Andrew, do you have a date for the next release?

Thanks,
-- 
-David
[email protected]

view thread (113+ messages)  latest in thread

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: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Re: Rewriting the test of pg_upgrade as a TAP test - take two
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox