This is the mail archive of the
mailing list for the Cygwin project.
Re: git on cygwin 1.7.2/1.7.4
- From: Mark Levedahl <mlevedahl at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 07 Apr 2010 22:43:08 -0400
- Subject: Re: git on cygwin 1.7.2/1.7.4
- References: <4BB29285.firstname.lastname@example.org> <20100331042545.GA23824@ednor.casa.cgf.cx> <4BB3F897.email@example.com>
On 03/31/2010 09:36 PM, Mark Levedahl wrote:
On 03/31/2010 12:25 AM, Christopher Faylor wrote:
Given the above, it seems logical the problem is with pipes, and as
1.7.4-1 is has fixes for pipes I tried it out and found a significant
improvement: using 1.7.2-1 I got 16 failures out of 20 attempts to clone
a 17 MByte repo on localhost, using 1.7.4-1 this is down to 3 failures
out of 20 attempts. (1.7.3-1 was not an improvement).
On Tue, Mar 30, 2010 at 08:08:37PM -0400, Mark Levedahl wrote:
All of the above connections and i/o processing are done using
bog-standard fork, pipe, open, read, write, and associated file
commands. Git has no trouble opening all of the processes and pipes
under Cygwin 1.7.2. However, in general before the data transfer is
complete the demux process issues an error upon getting an incomplete
packet (fewer bytes transmitted than declared in the header), and
debugging shows the error code of the read() is ENOENT, indicating the
pipe or socket has been terminated early. The index-pack process also
issues an error due to receipt of an incomplete pack.
The failures I do get are identical to what I described before: the
demux thread is getting a 0 (= EOF) return from read(stdin, ...), while
the server process is still trying to upload data via ssh.
So, 1.7.4-1 is better, but still has at least one issue remaining.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple