Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cOa13-0006LN-Cl for buildfarm-members@arkaria.postgresql.org; Wed, 04 Jan 2017 01:05:21 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cOa12-0000EX-Rm for buildfarm-members@arkaria.postgresql.org; Wed, 04 Jan 2017 01:05:20 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cOa0z-0000BO-QU for buildfarm-members@postgresql.org; Wed, 04 Jan 2017 01:05:17 +0000 Received: from mail-lf0-f46.google.com ([209.85.215.46]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cOa0s-00064A-LA for buildfarm-members@postgresql.org; Wed, 04 Jan 2017 01:05:17 +0000 Received: by mail-lf0-f46.google.com with SMTP id t196so296194893lff.3 for ; Tue, 03 Jan 2017 17:05:09 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2GA3wJIJ+k2MuLgORzPxMuDVrXSSvFrP71iXf1282O0=; b=RHPJMu1U7DdBuyP+I0tTGUMRGWwzNuXUSQQ8KDbWNrArf7gdQc9m9SMLJxOy5lHMu0 5BPMlglOTpVvihEdHNtXjwTStgywP/RhrAP8fcq+glBmP3h/w/owiIRAo1JqgmrSI7Py bSUfJ4el6W1gT6tmGh+j7MM0PpX3QSrshbATBz3TjvMrVCEXnPcsiAzzB6bLKIXeHOBr 4bQDzdSHxWZAbdyrIh8+wEWqBn4upmTZyVVbSI/9/mEJnKuV2CK/9oTIu6TcswEaj1PF ljTR97ya415mKgcQjokF+jxh3bv5R0H977Ae1knGTvkhMe6Rian8/IZ3UGK3PEBw9Fss dc6Q== X-Gm-Message-State: AIkVDXKm3cwnxw0AZZF+YgZo/6rm6Md2mgOduehl5HfDTTgBeib74lcpLKEQWz4rwyvzNUct6uEgHgC9/usaSg== X-Received: by 10.25.44.145 with SMTP id s139mr23099424lfs.176.1483491909406; Tue, 03 Jan 2017 17:05:09 -0800 (PST) MIME-Version: 1.0 References: <21316.1483482102@sss.pgh.pa.us> <9f59fc87-2694-f4a3-bd26-66c9d3362e7d@2ndQuadrant.com> In-Reply-To: <9f59fc87-2694-f4a3-bd26-66c9d3362e7d@2ndQuadrant.com> From: Stephen Frost Date: Wed, 04 Jan 2017 01:04:58 +0000 Message-ID: Subject: Re: git failures To: Andrew Dunstan , Tom Lane Cc: buildfarm-members@postgresql.org, craig@2ndquadrant.com, glyn.astill@seetickets.com Content-Type: multipart/alternative; boundary=001a1141021c49989205453a60db X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: buildfarm-members Precedence: bulk Sender: buildfarm-members-owner@postgresql.org --001a1141021c49989205453a60db Content-Type: text/plain; charset=UTF-8 All, I'm hopeful that I fixed it.... Thanks! Stephen On Tue, Jan 3, 2017 at 19:09 Andrew Dunstan wrote: > > > > > On 01/03/2017 05:21 PM, Tom Lane wrote: > > > Andrew Dunstan writes: > > >> Recently a number of git failures have been seen like this: > > >> *** Please tell me who you are. > > >> Notably on Debian/Ubuntu machines. I assume they have had some sort of > > >> recent git update. > > > No, I do not think it's the fault of the buildfarm machines. The problem > > > is that Magnus got rid of a bad commit into the 9.2 branch via "git > reset" > > > not "git revert", cf > > > > > > > https://www.postgresql.org/message-id/CABUevEzrD-BYtQOQ22navkoWquOC5TcqPcBS_iQ2cYqaK9_39g%40mail.gmail.com > > > > > > and these three machines seem to have been quick enough to see the > > > intermediate state and get confused by it. I'm not very sure why "git > > > pull" isn't enough to recover, but it evidently isn't. > > > > > > Yeah, axolotl just failed :-( > > > > cheers > > > > andrew > > > > -- > > Andrew Dunstan https://www.2ndQuadrant.com > > PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services > > > > --001a1141021c49989205453a60db Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
All,

I'm hopeful that I fixed it....

Thanks!

Stephen
On Tue, Jan 3, 2017 at 19:09 Andrew Dunsta= n <andrew.dunstan@2ndq= uadrant.com> wrote:




On 01/03/2017 05:21 PM, Tom= Lane wrote:

> Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
>> Recently a number of git failures have been seen like this:

>>=C2=A0 =C2=A0 =C2=A0 *** Please tell me who y= ou are.

>> Notably on Debian/Ubuntu machin= es. I assume they have had some sort of

>>= recent git update.

> No, I do not think it&#= 39;s the fault of the buildfarm machines.=C2=A0 The problem

> is that Magnus got rid of a bad commit into the 9.2 branch= via "git reset"

> not "git re= vert", cf

>

&= gt; https://www.postgresql.org/message-id/CABUevE= zrD-BYtQOQ22navkoWquOC5TcqPcBS_iQ2cYqaK9_39g%40mail.gmail.com

>

> and these three mac= hines seem to have been quick enough to see the

= > intermediate state and get confused by it.=C2=A0 I'm not very sure= why "git

> pull" isn't enough = to recover, but it evidently isn't.





Yeah, axolotl just failed := -(



cheers



andrew



--

Andrew Duns= tan=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 https://www.2ndQuadrant.com

PostgreSQL= Development, 24x7 Support, Remote DBA, Training & Services



--001a1141021c49989205453a60db--