Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Wed, 17 Mar 2004 11:58:26 -0500
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: latest snapshot seems better wrt make -j hang problems
Message-ID: <20040317165826.GA6542@redhat.com>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <20040313171440.GA7326@redhat.com> <c34on3$h5a$1@sea.gmane.org> <20040315173318.GB23853@redhat.com> <c39t2q$c7$1@sea.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <c39t2q$c7$1@sea.gmane.org>
User-Agent: Mutt/1.4.1i

On Wed, Mar 17, 2004 at 11:06:49AM -0500, Rolf Campbell wrote:
>Christopher Faylor wrote:
>>FWIW, I found ANOTHER race yesterday while running the cygwin test
>>suite.  So, it's back to square one for testing since it was in low
>>level code which could affect everything.  And, this race has been there
>>since I screwed up in September 2001.  Lovely.
>Well, I can't break the '16 snapshot either (> 11000 iterations without 
>any problems).  I'm guessing this included a fix for that other race you 
>speak of.

You wouldn't have seen the race.  It was tickled by another scenario in the
test suite -- one of the pthread_cond* tests, IIRC.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/