X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org F25B53857C55
Authentication-Results:	sourceware.org;
	dmarc=none (p=none dis=none) header.from=JC-Bell.com
Authentication-Results:	sourceware.org; spf=none smtp.mailfrom=Jim AT JC-Bell DOT com
Subject:	Re: python fails asyncio tests (py 3.7 & 3.8)
To:	cygwin AT cygwin DOT com
References:	<b7b31de6-1752-a705-a169-2ef1447fd93f AT JC-Bell DOT com>
From:	Jim Bell <Jim AT JC-Bell DOT com>
Organization:	J. C. Bell & Associates, Inc.
Message-ID:	<5233b4bb-8e9e-b6bd-0a56-c6ce5aa43f42@JC-Bell.com>
Date:	Sat, 21 Nov 2020 18:13:14 -0600
User-Agent:	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
	Thunderbird/78.5.0
MIME-Version:	1.0
In-Reply-To:	<b7b31de6-1752-a705-a169-2ef1447fd93f@JC-Bell.com>
X-Spam-Status:	No, score=-0.9 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 AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id 0AM0Dn22020772

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


--
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

- Raw text -