X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:references:to:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=iRx9RtEpHSJpX7JU
	zr+c19r597js/E5JiPaxmIlKEpODY32fCr+TDFuFLoY3MSHmkVU3yXqrXns1pn2B
	OREnaV6zIN+7YnHgfNBU3gGAEPSdnNB2Qs00bS4y3/ryecY+p8pDLPdo3cFaLqEi
	RF5F5SmMoWVlbQCPU0Kz4GlzVuw=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:references:to:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=/xQwaNPE3PsmtgMo+m5kY5
	qYos0=; b=JlFPM2+qYICtMmuTLaAE6WvkwmxwKc7WmH/BlMF6pMGNhMZbkM2aNR
	Z45xFzyk857gZ69AGf+Y15gx1T78ec9FJu7vbP0hK/WZ51djTEkJQgdYmJhyH1P2
	AwrqU3sx/ABgCq1Gjx85EGqPuRB4+GZSuoKoCdH0S25OyTiHjxANk=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=0.6 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=checkc, checkfortran, check-c, check-fortran
X-HELO:	csmail.cs.umass.edu
Reply-To:	moss AT cs DOT umass DOT edu
Subject:	Re: cygwin 2.5.0-0.12 questions, vim and nextafterl()
References:	<57054243 DOT 8080002 AT gmail DOT com> <20160406173132 DOT GA29221 AT calimero DOT vinschen DOT de> <5706279C DOT 3040302 AT gmail DOT com> <20160407123106 DOT GA6529 AT calimero DOT vinschen DOT de> <57065F25 DOT 7080407 AT aol DOT com>
To:	cygwin AT cygwin DOT com
From:	Eliot Moss <moss AT cs DOT umass DOT edu>
Message-ID:	<57066A1C.1080104@cs.umass.edu>
Date:	Thu, 7 Apr 2016 10:09:32 -0400
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version:	1.0
In-Reply-To:	<57065F25.7080407@aol.com>
X-IsSubscribed:	yes

On 4/7/2016 9:22 AM, Tim Prince wrote:

> In my experience, running multiple threads in make check by make -j 2
> results in the individual sessions make check-c, make check-c++ ...
> crashing and restarting endlessly.  Even when I run make -k check-c
> ,check-c++, check-fortran in separate bash windows, they usually die
> before completion.  I haven't tried for a while.

I suspect it strongly depends on the Makefile.  However, especially
when running checks, there may be implicit (unthinking) assumptions
that only one test runs at a time.  For example, if tests use the same
scratch directory, they're fine one at a time, but could easily get
into trouble with more than one at a time.

Regards -- EM

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

- Raw text -