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:reply-to
	:message-id:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=azQyLVxQJOkXdJzi
	+blV1ZtLjeMe+tpahifRs3E4QlVHWwCN+6Wx2mMNs7bC4r06wgNfkVlRRJQXPIKG
	AFshHpMdN8P1iT755amNBkHD68jQRmXSgZ2aOeqpbyfpiVk89Hd49izYeflVstyK
	rm3wbZBkqcjfibyrtW8aocI6gBw=
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:reply-to
	:message-id:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=0yxBPa3A+ue+nm5T2cBR5k
	eybhE=; b=S4jHbICRuL39CRbh8Lj6PPgUSlechLrSok27jxtBrwzaQaETo3KE32
	tsNhCjLs29yOEhicLwcBFZpN/0o68hAeSwqFOF93pa0BHnpPU8lGEk6ka59BfBzf
	6evQFCaN8whu5m4FJSFlHqzxwRq5SpgidA3G5j5alTiCSE3gNNYIo=
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=1.2 required=5.0 tests=AWL,BAYES_20,FREEMAIL_FROM,KAM_MXURI,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=no version=3.3.2 spammy=disastrous, H*F:D*aol.com, H*UA:6.3, H*u:6.3
X-HELO: omr-a011e.mx.aol.com
Reply-To: tprince AT computer DOT org
Subject: Re: Strange errors running gcc tests on Cygwin
References: <8fa02a72-e684-2ead-eacb-a5347d7594ae AT pobox DOT com> <82b31abc-7b7f-8f13-fc22-521c9ef84abf AT pobox DOT com> <8bda181f-f0bc-b0dc-2d2d-1bb17031ccee AT gmail DOT com> <b6c0f704-1f04-63ea-8220-ee30d623a9d6 AT pobox DOT com> <583230d9-f45c-aaa0-ed77-5c50863406f5 AT gmail DOT com> <9b872914-d9cf-378e-6eec-96c175a61ffe AT pobox DOT com> <ab35a49e-93e3-4384-bf81-3e8ac99b7194 AT gmail DOT com> <7372df4f-c55d-f9a3-325d-3f8800d67d98 AT pobox DOT com> <aab8c02e-2fe7-8ebf-5f3b-126e0ea0a745 AT gmail DOT com> <a7aca745-bbf2-a356-704a-4956ae6a28b3 AT pobox DOT com> <937197c6-f0cd-a7a0-a12f-d3f943ba2c1d AT SystematicSw DOT ab DOT ca> <affe4ca0-4677-6eb9-1d7d-94a129adc30c AT pobox DOT com> <53efff58-2f84-123a-95a4-a7c426c003ce AT SystematicSw DOT ab DOT ca>
To: cygwin AT cygwin DOT com
From: "Tim Prince via cygwin" <cygwin AT cygwin DOT com>
Reply-To: Tim Prince <n8tm AT aol DOT com>
Message-ID: <d0d8542e-d2c3-e2c4-e807-e740bd3a2979@aol.com>
Date: Thu, 9 Mar 2017 18:57:18 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <53efff58-2f84-123a-95a4-a7c426c003ce@SystematicSw.ab.ca>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
x-aol-global-disposition: G
x-aol-sid: 3039ac1b016258c1eccb505c
X-AOL-IP: 72.49.129.109



On 3/9/2017 6:51 PM, Brian Inglis wrote:
> On 2017-03-09 15:53, Daniel Santos wrote:
>
>>> If you are running a lot of Cygwin services, cron or Scheduled Tasks,
>>> and/or background processes, you may want to look at running cygserver
>>> to cache process info and common system info (including SAM/AD).
>> I'm only running sshd -- no cron or "at" jobs (except whatever
>> Windows installs by its self). However, gcc's make check spawns a LOT
>> of processes.
> Which was why I suggested it.
Even on linux, I don't find it satisfactory to run make check without
limiting processes to number of cores.  On cygwin and wsl, make check
seems to run into deadlocks or at least disastrous timeouts when running
multiple processes.  With a single process, cygwin runs it more reliably
than wsl does.  Conversely, sometimes (rarely) wsl can run make check-c
and make check-fortran simultaneously.
So it takes typically 2 full days to build and make check on cygwin.

-- 
Tim Prince


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