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-03 22:46:11
Message-ID: CAOuzzgomWboThBE9Nto7ZzsqMrB6nLyYT-1Aoy5ZgRdhAdBEtw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: buildfarm-members

Andrew, Tom,

Out of the office currently but will address as soon as I'm able to.

Thanks!

Stephen

On Tue, Jan 3, 2017 at 17:21 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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
>
>
>
>
> /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.
>
>
>
> regards, tom lane
>
>
>
>

In response to

Browse buildfarm-members by date

  From Date Subject
Next Message Andrew Dunstan 2017-01-04 00:08:49 Re: git failures
Previous Message Tom Lane 2017-01-03 22:21:42 Re: git failures