[issue8431] buildbot: hung on ARM Debian

STINNER Victor added the comment: There are no more ARM buildbots, so let's close this issue. -- resolution: -> out of date status: open -> closed ___ Python tracker ___ ___

[issue8431] buildbot: hung on ARM Debian

Antoine Pitrou added the comment: > the ARMv4 buildbot is a 500Mhz Xscale, with a SATA disk attached, 256MB > RAM. It can't go faster :-/ Have you checked running the test suite manually (possibly with the -v option for more progress information), to check whether these were genuine freezes?

[issue8431] buildbot: hung on ARM Debian

Matthias Klose added the comment: the ARMv4 buildbot is a 500Mhz Xscale, with a SATA disk attached, 256MB RAM. It can't go faster :-/ the ARMv7 buildbot is a cortex-a8, 500Mhz, 512MB RAM. I found here five or six python processes still running, now killed. The machine may be unresponsive som

[issue8431] buildbot: hung on ARM Debian

Antoine Pitrou added the comment: > Probably the timeout has to be increased drastically or -uall should > be dropped. We should probably increase the timeout on this particular set of buildbots. -uall has no influence on the duration of e.g. test_io. -- __

[issue8431] buildbot: hung on ARM Debian

Stefan Krah added the comment: I ran the whole test suite on http://people.debian.org/~aurel32/qemu/arm/debian_lenny_arm_small.qcow2 and there were no hanging processes. test_tokenize also takes around 10min on a fast machine (12s without -uall). Probably the timeout has to be increased drast

[issue8431] buildbot: hung on ARM Debian

STINNER Victor added the comment: It would help if regrtest.py added a timestamp to messages (at least "test_xxx" lines). Eg. "18:08:34.750933: test_io". -- ___ Python tracker _

[issue8431] buildbot: hung on ARM Debian

STINNER Victor added the comment: On ARMv7Thumb Ubuntu trunk, build 47 hung after the following tests: --- test_wait3 test_genericpath test_uuid test_zipimport_support test_slice test_decorators --- build 48 hung after the following tests: --- test_memoryio test_robotparser test_charmapcodec te

[issue8431] buildbot: hung on ARM Debian

Stefan Krah added the comment: Antoine is right: On a fast machine (3.16GHz) test_io.py takes 810s on debian-arm/qemu. All tests pass, so perhaps the limit is just too restrictive on slow machines. -- nosy: +skrah ___ Python tracker

[issue8431] buildbot: hung on ARM Debian

STINNER Victor added the comment: There are other hung on trunk (output of bbreport): ARMv4 Debian trunk 80129, 80120, 80101, 80098, 80085, 80129: # hung for 30 min: test_ast 80120: # hung for 30 min: test_descr 8010