From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7466 invoked by alias); 10 Mar 2017 00:01:24 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 7131 invoked by uid 89); 10 Mar 2017 00:01:18 -0000 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 Received: from omr-a011e.mx.aol.com (HELO omr-a011e.mx.aol.com) (204.29.186.59) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 10 Mar 2017 00:01:17 +0000 Received: from mtaout-aae02.mx.aol.com (mtaout-aae02.mx.aol.com [172.27.1.98]) by omr-a011e.mx.aol.com (Outbound Mail Relay) with ESMTP id 11EB0380009B for ; Thu, 9 Mar 2017 19:01:16 -0500 (EST) Received: from [192.168.200.215] (unknown [72.49.129.109]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mtaout-aae02.mx.aol.com (MUA/Third Party Client Interface) with ESMTPSA id 9036538000087 for ; Thu, 9 Mar 2017 19:01:15 -0500 (EST) Reply-To: tprince@computer.org Subject: Re: Strange errors running gcc tests on Cygwin References: <8fa02a72-e684-2ead-eacb-a5347d7594ae@pobox.com> <82b31abc-7b7f-8f13-fc22-521c9ef84abf@pobox.com> <8bda181f-f0bc-b0dc-2d2d-1bb17031ccee@gmail.com> <583230d9-f45c-aaa0-ed77-5c50863406f5@gmail.com> <9b872914-d9cf-378e-6eec-96c175a61ffe@pobox.com> <7372df4f-c55d-f9a3-325d-3f8800d67d98@pobox.com> <937197c6-f0cd-a7a0-a12f-d3f943ba2c1d@SystematicSw.ab.ca> <53efff58-2f84-123a-95a4-a7c426c003ce@SystematicSw.ab.ca> To: cygwin@cygwin.com From: "Tim Prince via cygwin" Reply-To: Tim Prince Message-ID: Date: Fri, 10 Mar 2017 00:01:00 -0000 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 X-SW-Source: 2017-03/txt/msg00127.txt.bz2 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