Issue 30643: test_basic_script_no_suffix() of test_multiprocessing_main_handling timeout after 20 min on Travis CI (original) (raw)

https://travis-ci.org/python/cpython/jobs/242108490#L2211

0:22:46 load avg: 62.38 [406/406/1] test_multiprocessing_main_handling crashed (Exit code 1)

Timeout (0:20:00)!

Thread 0x00002b175d341400 (most recent call first):

File "/home/travis/build/python/cpython/Lib/selectors.py", line 415 in select

File "/home/travis/build/python/cpython/Lib/subprocess.py", line 1488 in _communicate

File "/home/travis/build/python/cpython/Lib/subprocess.py", line 840 in communicate

File "/home/travis/build/python/cpython/Lib/test/support/script_helper.py", line 126 in run_python_until_end

File "/home/travis/build/python/cpython/Lib/test/support/script_helper.py", line 135 in _assert_python

File "/home/travis/build/python/cpython/Lib/test/support/script_helper.py", line 151 in assert_python_ok

File "/home/travis/build/python/cpython/Lib/test/test_multiprocessing_main_handling.py", line 157 in _check_script

File "/home/travis/build/python/cpython/Lib/test/test_multiprocessing_main_handling.py", line 169 in test_basic_script_no_suffix

File "/home/travis/build/python/cpython/Lib/unittest/case.py", line 605 in run

File "/home/travis/build/python/cpython/Lib/unittest/case.py", line 653 in call

File "/home/travis/build/python/cpython/Lib/unittest/suite.py", line 122 in run

File "/home/travis/build/python/cpython/Lib/unittest/suite.py", line 84 in call

File "/home/travis/build/python/cpython/Lib/unittest/suite.py", line 122 in run

File "/home/travis/build/python/cpython/Lib/unittest/suite.py", line 84 in call

File "/home/travis/build/python/cpython/Lib/unittest/suite.py", line 122 in run

File "/home/travis/build/python/cpython/Lib/unittest/suite.py", line 84 in call

File "/home/travis/build/python/cpython/Lib/unittest/runner.py", line 176 in run

File "/home/travis/build/python/cpython/Lib/test/support/init.py", line 1896 in _run_suite

File "/home/travis/build/python/cpython/Lib/test/support/init.py", line 1936 in run_unittest

File "/home/travis/build/python/cpython/Lib/test/libregrtest/runtest.py", line 164 in test_runner

File "/home/travis/build/python/cpython/Lib/test/libregrtest/runtest.py", line 165 in runtest_inner

File "/home/travis/build/python/cpython/Lib/test/libregrtest/runtest.py", line 119 in runtest

File "/home/travis/build/python/cpython/Lib/test/libregrtest/runtest_mp.py", line 71 in run_tests_slave

File "/home/travis/build/python/cpython/Lib/test/libregrtest/main.py", line 481 in _main

File "/home/travis/build/python/cpython/Lib/test/libregrtest/main.py", line 474 in main

File "/home/travis/build/python/cpython/Lib/test/libregrtest/main.py", line 538 in main

File "/home/travis/build/python/cpython/Lib/test/regrtest.py", line 46 in _main

File "/home/travis/build/python/cpython/Lib/test/regrtest.py", line 50 in

File "/home/travis/build/python/cpython/Lib/runpy.py", line 85 in _run_code

File "/home/travis/build/python/cpython/Lib/runpy.py", line 193 in _run_module_as_main

Should be fixed in PR #2139. Please reopen if not.

Thank you Antoine :-)

Hum, how do you feel about backporting recent Lib/multiprocessing/forkserver.py enhancements from master to 3.6 or even to 3.5? Do you consider them as bugfixes or more "enhancements"?

(If you want to backport, please wait after the 3.6.2 release to not stress our release manager, Ned Deily ;-))

Anointe: "Maintaining multiprocessing is quite delicate and I don't want to risk regressions in bugfix releases. If a bug is really annoying I would backport the fix, otherwise I'd rather abstain."

Honesty, same for me here :-D So ok, no backport yet ;-)