DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 50E0L4QQ3048816 Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 50E0L4QQ3048816 Authentication-Results: delorie.com; dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=E4clmXBM X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8FA91385800F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1736814063; bh=CN+RKI0PYp7RsweV/5YCSpMFtnhlC72NqAovcnvFHfM=; 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=E4clmXBMkvt8TIaN7b0QfUYwviUu1JgNVAwcKb1EA2LkWwiN/UBTMspQkIf9m2owP O7KHod6U/Z08jF+3YRxW2GaFP9pbREccfLEGoHxVYpKcLHM2U0kUaq1qT0NaOOhCqg mjgQjG3jtuTpO/Ftk9DDqEsN4PvAh4rhvHt3nOeA= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 1C1FC3858C5F ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 1C1FC3858C5F ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1736813594; cv=none; b=a7k8D/sZsD70X4nYggp4dF/vrdcrs/m2rGxoHZL04zMG6+6gMDoPimk8Y8fkRh4S+l1LS7srqf3rBpETLO3EGrVrgBC9LI8abzUtix550B0uXoEBrTkv2abR1XfntdfHthMrLFACdcWCjMBqo5NNQ58I7D4gKWMLb7hDudxnirc= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1736813594; c=relaxed/simple; bh=G7Fv1c/xUAAvI83AJMCSZ2wMsuAEGLd44iVlA1InTg8=; h=Date:From:To:Subject:Message-Id:Mime-Version:DKIM-Signature; b=Vg4JW30lFDkeNZF08FOhdUXdXCaVa4uSvvZtGCdOy7bi4X2csQe6yCNHDnJCcXXLmSvVeg/Y/ckKO77nHCe9rZlM93kuxUpyLFpfEuHmowsx/cxvcgn+8puIZ411jD/9kgtmdzwD67GA4yLqSIPgyHMjIYXKcu6sozGDydfKOQY= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1C1FC3858C5F Date: Tue, 14 Jan 2025 09:13:10 +0900 To: cygwin AT cygwin DOT com Subject: Re: Hangs in cygwin 3.5.5-1: should 3.5.5-1 be rolled back? Message-Id: <20250114091310.f1584810a0742417f2eb4c3e@nifty.ne.jp> In-Reply-To: <20250114085736.907bf487dfb51d0c5e11c402@nifty.ne.jp> References: <7d3aa20f-45b8-44a8-a353-a374d082c0b5 AT yahoo DOT de> <20250114085736 DOT 907bf487dfb51d0c5e11c402 AT nifty DOT ne DOT jp> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 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 Tue, 14 Jan 2025 08:57:36 +0900 Takashi Yano wrote: > Hi Michael, > > On Fri, 10 Jan 2025 08:48:00 +0100 > Michael Soegtrop wrote: > > sending again, since this did not appear in the archives ... > > > > Dear Cygwin Team, > > > > I wanted to discuss the status of the hangs in cygwin 3.5.5-1 discussed > > in various threads here. I maintain the multi platform distribution of > > the Rocq/Coq Proof Assistant, and the day cygwin 3.5.5 was released (Dec > > 20) our CI broke. Success rate of individual jobs is now roughly 50% > > with half failing with hangs at random points in the build. I verified > > that between the last good and the first bad CI run only cygwin itself > > changed (no other packages). > > > > I looked into this locally with procmon and to me it looks like a call > > to make is finished, shuts down its threads but then never terminates. I > > can reproduce this fairly easily - a few minutes after an initial setup > > of about 1/2 hour, which can be reused. But it is not reproducible in a > > single run - it is a random effect. To make it reproducible, I have to > > repeat a build step until it fails. But this always happens fairly soon. > > > > IMHO cygwin 3.5.5 is severely broken. Either a fix for these hangs also > > others experience should be released soon, or 3.5.5 should be rolled > > back until it is fixed. > > > > I definitely cannot make a release for Rocq/Coq Platform with cygwin 3.5.5. > > > > I want to take the opportunity to emphasize that in general cygwin is > > very stable and such issues are rare - I am running a nightly CI of > > Rocq/Coq Platform - a complex project which takes hours to build - with > > the latest cygwin since about 7 years and there were only few issues in > > this time. Thank you for your continued efforts! > > > > Do you think it would make sense to have a collection of CIs of large > > projects running daily on latest cygwin? If several of these break after > > a release of cygwin, this would give you an early warning that things > > might not be in good shape. I usually don't suspect cygwin if my CI > > breaks, so it usually takes me quite a while to figure this out. But if > > several projects break, this is more obvious and faster to analyze and > > to fix. > > We are very sorry for inconvinience. > Personally, I personally prefer releasing 3.5.6 ASAP. However, we > are not sure that we have already fixed all the major problems in > 3.5.5. > > Can you please test latest cygwin 3.6.0 (TEST) whether the your > CI issue still happens? As a side note, you can install cygwin 3.6.0 (TEST) by specifying the -t option to setup-x86_64.exe. -- 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