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 xtreak
Recipients pablogsal, vstinner, xtreak
Date 2019-03-24.07:35:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1553412920.81.0.155092332299.issue36414@roundup.psfhosted.org>
In-reply-to
Content
I am not able to reproduce the errors on GCC built CPython binary and running tests with virtualenv (no coverage). Seems the dangling thread error takes up the whole 50 minutes time limit. Since GCC build is not maintained or tracked is it worth stopping it on Travis since this wastes a lot of build minutes. Clang on Mac optional build never starts running the tests too.

Reference build failures : 

https://travis-ci.org/python/cpython/jobs/510447289
https://travis-ci.org/python/cpython/jobs/510447290
History
Date User Action Args
2019-03-24 07:35:20xtreaksetrecipients: + xtreak, vstinner, pablogsal
2019-03-24 07:35:20xtreaksetmessageid: <1553412920.81.0.155092332299.issue36414@roundup.psfhosted.org>
2019-03-24 07:35:20xtreaklinkissue36414 messages
2019-03-24 07:35:15xtreakcreate