Re: git failures

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: buildfarm-members(at)postgresql(dot)org, craig(at)2ndquadrant(dot)com, glyn(dot)astill(at)seetickets(dot)com
Subject: Re: git failures
Date: 2017-01-04 01:04:58
Message-ID: CAOuzzgqT7LQyn+bUKp_b8p2DGGqYk5TwAH7zWgGOUZXCkVX-PQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: buildfarm-members

All,

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

Thanks!

Stephen

On Tue, Jan 3, 2017 at 19:09 Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
wrote:

>
>
>
>
> On 01/03/2017 05:21 PM, Tom Lane wrote:
>
> > Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> 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
>
>
>
>

In response to

Responses

Browse buildfarm-members by date

  From Date Subject
Next Message Tom Lane 2017-01-04 01:24:50 Re: git failures
Previous Message Andrew Dunstan 2017-01-04 00:08:49 Re: git failures