New submission from STINNER Victor:

> ./python  ./Tools/scripts/run_tests.py -j 1 -u all -W --slowest --timeout=900 
> -j2 -j8

faulthandler was supposed to kill test_pydoc after 15 minutes, and regrtest is 
supposed to log "running: pydoc (since xxx seconds)" every 30 seconds. 
Something gone bad. Buildbot killed regrtest because it didn't produce output 
during 20 minutes.

http://buildbot.python.org/all/builders/ARMv7%20Ubuntu%203.x/builds/968/steps/test/logs/stdio

running: test_pydoc (420 sec), test_datetime (234 sec), test_tools (258 sec)
0:11:42 load avg: 3.90 [404/406] test_datetime passed (240 sec) -- running: 
test_pydoc (428 sec), test_tools (266 sec)
running: test_pydoc (458 sec), test_tools (296 sec)
0:12:13 load avg: 3.15 [405/406] test_tools passed (296 sec) -- running: 
test_pydoc (459 sec)

command timed out: 1200 seconds without output running ['make', 'buildbottest', 
'TESTOPTS=-j2 -j8', 'TESTPYTHONOPTS=', 'TESTTIMEOUT=900'], attempting to kill
process killed by signal 9
program finished with exit code -1
elapsedTime=1936.512343

----------
components: Tests
keywords: buildbot
messages: 296861
nosy: haypo
priority: normal
severity: normal
status: open
title: test_pydoc (regrtest?) hangs on ARMv7 Ubuntu 3.x
versions: Python 3.7

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

Reply via email to