X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-0.3 required=5.0	tests=AWL,BAYES_00,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
To: cygwin@cygwin.com
Subject: Re: YA call for snapshot testing
In-reply-to: <20120125062835.GD18425@ednor.casa.cgf.cx>
References: <20120122054719.GB28773@ednor.casa.cgf.cx> <20120122055300.GB657@ednor.casa.cgf.cx> <4F1BBB0F.2020009@gmail.com> <20120122165705.GA10996@ednor.casa.cgf.cx> <4F1C5F56.8070208@gmail.com> <20120122193306.GA12886@ednor.casa.cgf.cx> <4F1C759D.9010704@shaddybaddah.name> <29235.1327446059@freon.franz.com> <4F1F422E.9040507@cygwin.com> <13884.1327471385@freon.franz.com> <20120125062835.GD18425@ednor.casa.cgf.cx>
Comments: In-reply-to Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>   message dated "Wed, 25 Jan 2012 01:28:35 -0500."
Date: Wed, 25 Jan 2012 11:58:44 -0800
Message-ID: <22712.1327521524@freon.franz.com>
From: Kevin Layer <layer@franz.com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

Christopher Faylor wrote:

>> On Tue, Jan 24, 2012 at 10:03:05PM -0800, Kevin Layer wrote:
>> >Larry Hall (Cygwin) wrote:
>> >
>> >>> > This problem is killing me.  I'm currently looking msysgit + GnuWin32
>> >>> > because I just can't take the crashes of bash.exe and git.exe anymore.
>> >>> > In my testing, so far, I've never seen msysgit or the bash that comes
>> >>> > with it crash.  Why is it that cygwin has this problem but msysgit
>> >>> > does not?  It's an honest question and I'm not trying to be
>> >>> > provocative.  I've been a cygwin user since before Red Hat acquired
>> >>> > them, and the above statement makes me really sad.
>> >>> 
>> >>> Have you tried running rebaseall?  
>> >
>> >Absolutely.  After updating cygwin, I reboot and run rebaseall -v
>> >first thing.
>> 
>> FYI, as far as I can tell the stack trace that you provided did not seem
>> to come from the 20120123 snapshot.

OK, I didn't have the snapshot installed.  It was the 1.7.9 dll.  I
had copied it in, then found I couldn't start bash, backed out the
change, and rebooted, but I guess I forgot to redo it.

I just installed it and did some testing, and it seems to be working
OK.

I'll report back if I see another crash.  I just ran this test, in
parallel on 4 different source trees (each composed of 52 repos):
  git fetch origin
  git rebase origin/master
  git status

and not a single crash.  It's usually good for 3-5 crashes, if I do
them in parallel like that.

Fingers crossed.

NOTE: I run with CYGWIN="nodosfilewarning proc_retry:1" because I run
a lot of non-cygwin software from shell scripts, and during testing,
that can take 10's of minutes, I can't afford to have those programs
restarted if they crash on exit.  Before setting proc_retry:1, I once
saw a loop of a 30 minute test run that went on for 10+ iterations.

It would be really nice if you could apply proc_retry to cygwin
programs only.  Would that be possible?  Then, I could remove that
setting from CYGWIN and life would probably be better for me.


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

