[issue36414] Multiple test failures in GCC and Clang optional builds on Travis CI

Change by Xavier de Gaye : -- nosy: -xdegaye ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36414] Multiple test failures in GCC and Clang optional builds on Travis CI

STINNER Victor added the comment: I looked at at recent PR. It's getting better. "Test code coverage (C)" fails with: == ERROR: test_build_ext (distutils.tests.test_build_ext.BuildExtTestCase)

[issue36414] Multiple test failures in GCC and Clang optional builds on Travis CI

Karthikeyan Singaravelan added the comment: The builds are now running since issue36684 changed the build process splitting the coverage and there are now three test failures in test_gc, test_descr and test_typing (issue36905) unrelated to the original report :

[issue36414] Multiple test failures in GCC and Clang optional builds on Travis CI

Xavier de Gaye added the comment: FWIW PR 12708 has been merged. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue36414] Multiple test failures in GCC and Clang optional builds on Travis CI

Karthikeyan Singaravelan added the comment: https://github.com/python/cpython/pull/12708 that seems to fix similar issue (issue36544) for Ubuntu that helps in making Mac OS build green again. Successful build : https://travis-ci.org/python/cpython/jobs/516821454 -- nosy: +xdegaye

[issue36414] Multiple test failures in GCC and Clang optional builds on Travis CI

Karthikeyan Singaravelan added the comment: https://bugs.python.org/issue36414#msg338876 > Travis CI config has been changed to use a more recent Ubuntu version, it can > explain the failure. I am confused since the commit changes the linux build to use xenial but the failure is on Mac OS

[issue36414] Multiple test failures in GCC and Clang optional builds on Travis CI

STINNER Victor added the comment: > Possibly first occurrence of this error : > https://travis-ci.org/python/cpython/jobs/506783665 after which it's more or > less consistent. That's the first build including my change: commit 86082c22d23285995a32aabb491527c9f5629556 Author: Victor Stinner

[issue36414] Multiple test failures in GCC and Clang optional builds on Travis CI

STINNER Victor added the comment: > https://travis-ci.org/python/cpython/jobs/510447290 That's a run on the master branch ("CRON"). xvfb-run ./venv/bin/python -m coverage run --pylib -m test --fail-env-changed -uall,-cpu -x test_multiprocessing_fork -x test_multiprocessing_forkserver -x

[issue36414] Multiple test failures in GCC and Clang optional builds on Travis CI

STINNER Victor added the comment: > https://travis-ci.org/python/cpython/jobs/510447289 This failure is on the master branch. ./python.exe ./Tools/scripts/run_tests.py -j 1 -u all -W --slowest --fail-env-changed --timeout=1200 -j4 -uall,-cpu ERROR:root:code for hash md5 was not found.

[issue36414] Multiple test failures in GCC and Clang optional builds on Travis CI

Karthikeyan Singaravelan added the comment: Possibly first occurrence of this error : https://travis-ci.org/python/cpython/jobs/506783665 after which it's more or less consistent. Almost all the builds I checked before this build did not have this failure. The commit for the build seems to

[issue36414] Multiple test failures in GCC and Clang optional builds on Travis CI

New submission from Karthikeyan Singaravelan : 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