X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.6 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com Subject: Re: "git clone" over ssh fails intermittently w/snapshot 20120123 In-reply-to: <20120130161649.GA8413@ednor.casa.cgf.cx> References: <26758 DOT 1327703355 AT freon DOT franz DOT com> <26967 DOT 1327703574 AT freon DOT franz DOT com> <20120128183816 DOT GA24438 AT ednor DOT casa DOT cgf DOT cx> <4332 DOT 1327939546 AT freon DOT franz DOT com> <20120130161649 DOT GA8413 AT ednor DOT casa DOT cgf DOT cx> Comments: In-reply-to Christopher Faylor message dated "Mon, 30 Jan 2012 11:16:49 -0500." Date: Mon, 30 Jan 2012 13:39:35 -0800 Message-ID: <16161.1327959575@freon.franz.com> From: Kevin Layer X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Christopher Faylor wrote: >> On Mon, Jan 30, 2012 at 08:05:46AM -0800, Kevin Layer wrote: >> >Christopher Faylor wrote: >> >>> Is this new behavior just seen with this snapshot or is it something you >> >>> noticed in 1.7.9? If you've just seen it in the latest snapshot it >> >>> would be useful (as I've previously pleaded) to know in which snapshot >> >>> the bad behavior first showed up. >> > >> >Never seen until the snapshot was installed. >> >> That isn't precise enough. Are you saying that you saw the problem in >> the 2012-01-23 snapshot but not in the 2012-01-22 snapshot? I'll bet >> that you aren't. If you think this is a problem only manifested in >> snapshots then we need to know which snapshot first had the >> problem. No. I didn't see it in 1.7.9, but do see it in the referenced snapshot. >> >More info: >> > >> >Before the failure, I had removed and reinstalled cygwin, then >> >installed the snapshot. The machine on which git works was upgraded >> >little at a time. >> >> OTOH, "little at a time" might mean that you stepped through >> snapshots. No, I meant that the machine on which I've never seen the failure, even with the same 1/23 snapshot, had the packages on it upgraded once a month (roughly). I didn't remove everything and reinstall once a month, for example. On the machine that I have seen the errors, I removed everything, because I was in a weird state with my msysgit testing, so I thought it best to start from scratch. I removed msysgit and gnuwin32, as well. >> However, since the only change to 2012-01-23 was to tweak fifos and, as >> far as I know, git clone doesn't use a fifo, it's hard to see why there >> would be a regression in 2012-01-23. If you can think of some other tests I could perform, I'd be happy to do it. The machine with the failures is not a critical development machine, so it's pretty open to what I can do. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple