From: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Subject: Re: git failures
To: Tom Lane <tgl@sss.pgh.pa.us>
References: <ede85945-5151-3874-dde6-ff35b8dd76f0@2ndQuadrant.com>
 <21316.1483482102@sss.pgh.pa.us>
Cc: sfrost@snowman.net, glyn.astill@seetickets.com, craig@2ndquadrant.com,
 buildfarm-members@postgresql.org
Message-ID: <9f59fc87-2694-f4a3-bd26-66c9d3362e7d@2ndQuadrant.com>
Date: Tue, 3 Jan 2017 19:08:49 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <21316.1483482102@sss.pgh.pa.us>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: buildfarm-members-owner@postgresql.org


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:
>>      *** 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


-- 
Sent via buildfarm-members mailing list (buildfarm-members@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/buildfarm-members