➜

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-02-12.17:37:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1549993072.6.0.794740252515.issue35978@roundup.psfhosted.org>
In-reply-to
Content 
I noticed this while checking issue35961. test_venv is always failing on GCC which is marked as optional in Travis.

Log : https://travis-ci.org/python/cpython/jobs/492123436#L1909

0:39:35 load avg: 1.00 [390/416] test_venv
test test_venv failed -- Traceback (most recent call last):
  File "/home/travis/build/python/cpython/Lib/test/test_venv.py", line 309, in test_multiprocessing
    out, err = check_output([envpy, '-c',
  File "/home/travis/build/python/cpython/Lib/test/test_venv.py", line 37, in check_output
    raise subprocess.CalledProcessError(
subprocess.CalledProcessError: Command '['/tmp/tmpg8ubeyfn/bin/python', '-c', 'from multiprocessing import Pool; print(Pool(1).apply_async("Python".lower).get(3))']' died with <Signals.SIGABRT: 6>.

Also GCC test have been timing out for at least past 4 months : https://python.zulipchat.com/#narrow/stream/116742-core.2Fhelp/topic/GCC.20build.20in.20Travis.20always.20times.20out
History
Date User Action Args
2019-02-12 17:37:52xtreaksetrecipients: + xtreak, vstinner, pablogsal
2019-02-12 17:37:52xtreaksetmessageid: <1549993072.6.0.794740252515.issue35978@roundup.psfhosted.org>
2019-02-12 17:37:52xtreaklinkissue35978 messages
2019-02-12 17:37:52xtreakcreate