| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
| Cc: | sfrost(at)snowman(dot)net, glyn(dot)astill(at)seetickets(dot)com, craig(at)2ndquadrant(dot)com, buildfarm-members(at)postgresql(dot)org |
| Subject: | Re: git failures |
| Date: | 2017-01-03 22:21:42 |
| Message-ID: | 21316.1483482102@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | buildfarm-members |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2017-01-03 22:46:11 | Re: git failures |
| Previous Message | Andrew Dunstan | 2017-01-03 22:16:57 | git failures |