From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from m0.truegem.net (m0.truegem.net [69.55.228.47]) by sourceware.org (Postfix) with ESMTPS id ACB02385780E for ; Tue, 1 Dec 2020 00:53:53 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org ACB02385780E Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=maxrnd.com Authentication-Results: sourceware.org; spf=none smtp.mailfrom=mark@maxrnd.com Received: (from daemon@localhost) by m0.truegem.net (8.12.11/8.12.11) id 0B10rqk1030833; Mon, 30 Nov 2020 16:53:52 -0800 (PST) (envelope-from mark@maxrnd.com) Received: from 162-235-43-67.lightspeed.irvnca.sbcglobal.net(162.235.43.67), claiming to be "[192.168.1.100]" via SMTP by m0.truegem.net, id smtpdLs8sw0; Mon Nov 30 16:53:43 2020 Subject: Re: python fails asyncio tests (py 3.7 & 3.8) To: Jim Bell , cygwin@cygwin.com References: <5233b4bb-8e9e-b6bd-0a56-c6ce5aa43f42@JC-Bell.com> From: Mark Geisert Message-ID: Date: Mon, 30 Nov 2020 16:53:43 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 MIME-Version: 1.0 In-Reply-To: <5233b4bb-8e9e-b6bd-0a56-c6ce5aa43f42@JC-Bell.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-5.1 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Dec 2020 00:53:57 -0000 Hi Jim, Jim Bell wrote: > On 2020-11-21 5:59 AM, Jim Bell wrote: >> The standard python asyncio tests hang. >> >>         cd /usr/lib/python3.8/test >> >>         python3.8 test_asyncore.py -v >> >> [...] > > > Using strace, stripping down this very repeatable test, and grabbing the > source-code snapshot, it looks like winsup/cygwin/select.cc socket_cleanup() is > waiting forever for the thread to go away. > > strace: > >   121 6732185 [main] python3.8 13329 select_stuff::cleanup: calling cleanup rout > ines >   178 6732363 [main] python3.8 13329 socket_cleanup: si 0x800290E10 si->thread 0 > x18023E758 > - > > But I don't see the select_printf("returning")  at select.cc:1808, so the > si->thread->detach() call seems to be blocked forever.  I don't see that we make > it here either: > >     select.cc:1685  select_printf ("leaving thread_socket"); > > I see a bool stop_thread field in select_info, inherited by select_socket_info > (select.h), used by other mechanisms. Seems that could be set by socket_cleanup() > and used by thread_socket() to break out of its event loops (select.cc lines 1660 > and 1667) > > https://cygwin.com/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/select.cc;hb=HEAD#l1796 Thanks for the report and especially for the initial debugging you've done. I've reproduced the issue on my test machine. No need to supply 'cygcheck -svr' at this point. I'll investigate this further and keep you posted (on the Cygwin mailing list). ..mark