➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author db3l
Recipients Ben.Darnell, Burak Yiğit Kaya, Jonathan Slenders, PeterL777, Rustam S., Segev Finer, asvetlov, cjrh, cmeyer, db3l, miss-islington, steve.dower, yselivanov
Date 2020-09-01.21:32:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1598995975.43.0.322210697251.issue39010@roundup.psfhosted.org>
In-reply-to
Content 
I've been seeing failures on the Win10 buildbot 3.x branch that seem to correlate with the timing of this change - could there be some further work needed on Windows?  Or, if it's a test-only artifact and the warnings are innocuous, something to ignore the output during the tests?

Specifically, the following warnings occur during test_asyncio:
   Warning -- threading_cleanup() failed to cleanup 1 threads (count: 1, dangling: 2)
   Warning -- Dangling thread: <_MainThread(MainThread, started 5220)>

See https://buildbot.python.org/all/#/builders/146/builds/23 for the first failing build.
History
Date User Action Args
2020-09-01 21:32:55db3lsetrecipients: + db3l, asvetlov, cjrh, Ben.Darnell, yselivanov, steve.dower, cmeyer, Segev Finer, miss-islington, PeterL777, Jonathan Slenders, Rustam S., Burak Yiğit Kaya
2020-09-01 21:32:55db3lsetmessageid: <1598995975.43.0.322210697251.issue39010@roundup.psfhosted.org>
2020-09-01 21:32:55db3llinkissue39010 messages
2020-09-01 21:32:55db3lcreate