Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Date: Thu, 23 Jan 2003 21:51:43 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: ARGH  pthreads tests failing?
Message-ID: <20030124025143.GA1962@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <20030122150338 DOT GA4396 AT redhat DOT com> <Pine DOT WNT DOT 4 DOT 44 DOT 0301230837570 DOT 213-100000 AT algeria DOT intern DOT net> <20030123163224 DOT GA11997 AT redhat DOT com> <20030123201039 DOT GA20854 AT redhat DOT com> <1043352929 DOT 27382 DOT 13 DOT camel AT lifelesslap> <20030124022645 DOT GA14591 AT redhat DOT com> <20030124023217 DOT GA30080 AT redhat DOT com> <20030124023405 DOT GA1814 AT redhat DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030124023405.GA1814@redhat.com>
User-Agent: Mutt/1.5.1i

On Thu, Jan 23, 2003 at 09:34:05PM -0500, Christopher Faylor wrote:
>On Thu, Jan 23, 2003 at 09:32:17PM -0500, Christopher Faylor wrote:
>>On Thu, Jan 23, 2003 at 09:26:45PM -0500, Christopher Faylor wrote:
>>>On Fri, Jan 24, 2003 at 07:15:29AM +1100, Robert Collins wrote:
>>>>On Fri, 2003-01-24 at 07:10, Christopher Faylor wrote:
>>>>>How do we proceed here?  I also get this kind of error if I build
>>>>>everything from scratch and do the standard make; make check.
>>>>
>>>>Those errors are a result of the change to the default mutex type.  We
>>>>should update the tests.
>>>
>>>Hmm.  After taking an exhaustive sweep over the whole testsuite and
>>>eliminating all warnings (some of which were actually indicative of
>>>errors), everything seems to be working ok, now.
>>>
>>>I'm doing my 50th testsuite run to verify this but it looks like I'll
>>>be releasing 1.3.19 soon.
>>
>>Of course the mutex failures came back with this run.  Could they possibly
>>be sporadic?
>
>Ah.  I see the difference.  I erroneously had optimization turned on in the
>last test suite run.  I turned it off and got the aforementioned errors.
>
>Perhaps this is a hint.

Don't pay any attention to me.  This was a reversion due to the fact
that I had made a change to my "improved" makefile and was no longer
passing the correct CFLAGS to the build process.  Phew.

I'll stop typing now.  This looks good.  Sorry for the chatter.

AFAICT, the problem went away when I changed the testsuite makefile
to use all of the same flags as everything else in winsup.

cgf