X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B3FA43858402 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1710670903; bh=lLBiMMUS7QsaKwJrQR+YaAfrofHSZkEKg4Sr66OczRE=; h=Date:To:Cc:Subject:In-Reply-To:References:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=TSZLuMBMElbc+vLblYKa07cihc/xvcjQfBUIXFQDZPVCILBDcu5QzneQO6ys9hLR/ vZuI01oLvOqpa2PMKfqYGCje2Ovz/Y+nsCgKWytNRRrqbmU6Vw1NIbtRlJrbwaLPHD FpScG2Z68RglN59oLhHWYDzLJCKgtGWGXRXFXkJU= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 54D5E3858CD1 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 54D5E3858CD1 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1710670882; cv=none; b=DL2qOp3qzuHr/qjjaxDrij38Z0Yxe18sw+AghSJf+dr9VBqei42XX3T9tMBwppHP1w4zYDMSMkpsWvXVq+EC6Ae5mXdnvJ+O+TO0l1Z1pQX9O6YQ3+MDO5eqsCuN3LJ63gtxdTDTEhi7jbOWuBzrkSr2QL/+yEoG+JOd88aq5Zk= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1710670882; c=relaxed/simple; bh=1B282J987i13f4xyQuTIyqzcTeJh/PEDH1GVti3B3xc=; h=Date:From:To:Subject:Message-Id:Mime-Version; b=usoZ+9LcJJ93LYW7l/Z4huEl8bpL7ByjD++JKIXkttqwitAsgK2dw9nqynWkcHtgvdo6kijK1ONMz4B0pbB1niM3VCwAgjAYGaekouWespafs61zQX8X4J5nXW5hPZKhirMFPv67ck5ka2Kno1JN+iPVxQ7vNWwa2UeZK8pQndc= ARC-Authentication-Results: i=1; server2.sourceware.org Date: Sun, 17 Mar 2024 19:21:16 +0900 To: cygwin AT cygwin DOT com Cc: Alexey Izbyshev Subject: Re: Bogus exit code 127 from a child process Message-Id: <20240317192116.b00f24c9ee065f16d6ac6673@nifty.ne.jp> In-Reply-To: References: <20240317174402 DOT 4a3e73a7fca2f5978ac93913 AT nifty DOT ne DOT jp> <61d4fca73047915567fc9b4aac2860a3 AT ispras DOT ru> <20240317182757 DOT 84b41a596c344f395c1d8f9a AT nifty DOT ne DOT jp> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 X-Spam-Status: No, score=-4.9 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Takashi Yano via Cygwin Reply-To: Takashi Yano Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" On Sun, 17 Mar 2024 13:03:40 +0300 Alexey Izbyshev wrote: > On 2024-03-17 12:27, Takashi Yano wrote: > > On Sun, 17 Mar 2024 12:01:55 +0300 > > Alexey Izbyshev wrote: > >> On 2024-03-17 11:44, Takashi Yano wrote: > >> > On Sun, 17 Mar 2024 11:14:16 +0300 > >> > Alexey Izbyshev wrote: > >> >> Hello, > >> >> > >> >> I've been getting occasional "Error 127" from make -jN on seemingly > >> >> random jobs. After reducing the set of jobs and eventually eliminating > >> >> make, I've arrived to this one-liner: > >> >> > >> >> bash -c 'true & true & wait -n || echo 1: $? && wait -n || echo 2: $?' > >> >> > >> >> When run repeatedly, the second "wait -n" often reports 127. > >> >> > >> >> I've reproduced this in the following environments: > >> >> > >> >> * Cygwin 3.5.1, Windows 10 22H2 x64 > >> >> * Cygwin 3.4.6, Windows 10 22H2 x64 and Windows 7 x64 > >> >> > >> >> I couldn't reproduce it in Cygwin 3.3.6 (WOW64) on Windows 7 x64. > >> > > >> > Could you please try latest cygwin 3.6.0 (TEST) ? > >> > >> Tested with 3.6.0-0.82.gfc691d0246b9 on Windows 10 22H2 x64, the > >> problem > >> still occurs. > > > > In my evrironmen, trial for 1 hour does not reproduce the issue. > > Could you please let us know your environment, i.e. CPU, amount of > > memory, and so on? > > It's been reproduced in a variety of environments: > > * Windows 10 22H2 x64, Intel Core i7 11700, 32 GB RAM > * Windows 10 22H2 x64, Intel Core i7 9700, 32 GB RAM > * Windows 10 22H2 x64, Intel Core i7 6700, 32 GB RAM > * Windows 7 SP1 x64, Intel Core i7 6700, 32 GB RAM > > I'm surprised that you're not hitting it very quickly. The following > loop usually fails after a few iterations (rarely a hundred or so) in my > tests: > > while bash -c 'true & true & wait -n || { echo 1: $?; exit 1; } && wait > -n || { echo 2: $?; exit 1; }'; do echo $((i++)); done Thanks. My main PC still runs the above test for more than 15000 counts. So, I tried another PC which CPU is Core i5 540M and could reproduce the issue about 1 time per a few hundreds count. I also tried to run sleep 0.1 instead of true, then, the issue happens 1 time per a few decades counts. I'll look into this problem. Thanks for the report. -- Takashi Yano -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple