New submission from Karthikeyan Singaravelan <tir.kar...@gmail.com>:

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

----------
components: Tests
messages: 338725
nosy: pablogsal, vstinner, xtreak
priority: normal
severity: normal
status: open
title: Multiple test failures in GCC and Clang optional builds on Travis CI
type: behavior
versions: Python 3.8

_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue36414>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to