X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2AD9B3858D32 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1710677067; bh=ryq7uZHQApRmcsBb9CLJox1DGFxnXUn6hpaBqCUaU50=; h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=wWPNXGeDMZAIfxPA6cYFqIJVsm84x4aGy1HZlwsVjHfLJ2dRmpo2/vak8tSc4Dgyb M2k+7MI8gbN9JmqbleeISciI0qWv/a4nb6VPSfRg77KN7IWccSdTnX41D+JhGonGZ+ QgqN1hsQJq/huuOjX51tM2/CzKIQnhL16+Lj+N1Y= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 06ACD3858D32 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 06ACD3858D32 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1710677044; cv=none; b=syPi3fWj0KbISJKjG73r8alVgRDowEP9aST+OP0WHZasvEwMKth1xWkFCasE0vUiTMPZGMVtfRDVlkPEOrM2juay2aCb/+Sn0SpLp5LRtjHcsdW1nBdiMVKzUXvk7eNHXoPAe+9tQHkPt7P8QjeQtUgsSugBlZT0ipEvxB5MeOY= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1710677044; c=relaxed/simple; bh=tGIQ/bqOWxFyXvIahWsFo1CiiNlLl4f1IMN2fPbN7Nc=; h=Date:From:To:Subject:Message-Id:Mime-Version; b=kIpes1/8LTsVa1rfpIJorj3HbHC6aj3rFH8yzMdkxjG9k66MumU6jd2Y2rm4xbRTwwu42Fl1sNUXfHMCzNbtSH+Hxno/pk+6YoMGfV+X2ampGkictyn2DOxs//ge2RyIH04Nd6sMdvUa6mHKfZGVVy9bwvygaIghDDmH+aFTOrE= ARC-Authentication-Results: i=1; server2.sourceware.org Date: Sun, 17 Mar 2024 21:03:58 +0900 To: cygwin AT cygwin DOT com Subject: Re: Bogus exit code 127 from a child process Message-Id: <20240317210358.ad701873dc5cfc9a3026dc0c@nifty.ne.jp> In-Reply-To: <20240317192116.b00f24c9ee065f16d6ac6673@nifty.ne.jp> References: <20240317174402 DOT 4a3e73a7fca2f5978ac93913 AT nifty DOT ne DOT jp> <61d4fca73047915567fc9b4aac2860a3 AT ispras DOT ru> <20240317182757 DOT 84b41a596c344f395c1d8f9a AT nifty DOT ne DOT jp> <20240317192116 DOT b00f24c9ee065f16d6ac6673 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, 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 19:21:16 +0900 Takashi Yano wrote: > 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. In my environment, the issue is reproducible even with cygwin 3.3.6 (32bit, i.e. WOW64) and bash 4.4.12(3)-release (i686-pc-cygwin). What are the versions of bash in each systems? -- 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