[issue11779] test_mmap timeout (30 min) on AMD64 Snow Leopard 3.x buildbot
STINNER Victor victor.stin...@haypocalc.com added the comment: Let's close this issue. I will reopen it if a timeout of 60 min was not the right choice to workaround this failure. -- resolution: - out of date status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11779 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11779] test_mmap timeout (30 min) on AMD64 Snow Leopard 3.x buildbot
STINNER Victor victor.stin...@haypocalc.com added the comment: Antoine changed regrtest default timeout to 60 minutes. It should workaround test_mmap timeout, so can we close this issue? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11779 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11779] test_mmap timeout (30 min) on AMD64 Snow Leopard 3.x buildbot
Ross Lagerwall rosslagerw...@gmail.com added the comment:
OS X filesystem does not support seeking ahead to create sparse files.
The test is supposed to skip the LargeMmapTests on OS X and Windows with (line
679 of test_mmap.py):
if sys.platform[:3] == 'win' or sys.platform == 'darwin':
requires('largefile', 'test requires %s bytes and a long time to run' %
str(0x18000))
Perhaps on the Snow Leopard buildbot something causes this line not to become
true (what does sys.platform give on the buildbot)?
As for why its creating the file slowly (encrypted fs?), I don't know but the
test shouldn't be running anyway...
--
nosy: +rosslagerwall
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11779
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11779] test_mmap timeout (30 min) on AMD64 Snow Leopard 3.x buildbot
Antoine Pitrou pit...@free.fr added the comment: Well, buildbots run tests with -uall, so the largefile resource gets enabled. -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11779 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11779] test_mmap timeout (30 min) on AMD64 Snow Leopard 3.x buildbot
New submission from STINNER Victor victor.stin...@haypocalc.com: The creation of a file of 5.25 GB took more than 30 min on AMD64 Snow Leopard 3.x buildbot, and so regrtest exited: - [ 27/354] test_mmap Thread 0x7fff70439ca0: File /Users/pythonbuildbot/buildarea/3.x.hansen-osx-x86/build/Lib/test/test_mmap.py, line 685 in test_large_offset File /Users/pythonbuildbot/buildarea/3.x.hansen-osx-x86/build/Lib/unittest/case.py, line 387 in _executeTestPart File /Users/pythonbuildbot/buildarea/3.x.hansen-osx-x86/build/Lib/unittest/case.py, line 442 in run File /Users/pythonbuildbot/buildarea/3.x.hansen-osx-x86/build/Lib/unittest/case.py, line 494 in __call__ File /Users/pythonbuildbot/buildarea/3.x.hansen-osx-x86/build/Lib/unittest/suite.py, line 105 in run File /Users/pythonbuildbot/buildarea/3.x.hansen-osx-x86/build/Lib/unittest/suite.py, line 67 in __call__ File /Users/pythonbuildbot/buildarea/3.x.hansen-osx-x86/build/Lib/unittest/suite.py, line 105 in run File /Users/pythonbuildbot/buildarea/3.x.hansen-osx-x86/build/Lib/unittest/suite.py, line 67 in __call__ File /Users/pythonbuildbot/buildarea/3.x.hansen-osx-x86/build/Lib/test/support.py, line 1078 in run File /Users/pythonbuildbot/buildarea/3.x.hansen-osx-x86/build/Lib/test/support.py, line 1166 in _run_suite File /Users/pythonbuildbot/buildarea/3.x.hansen-osx-x86/build/Lib/test/support.py, line 1192 in run_unittest File /Users/pythonbuildbot/buildarea/3.x.hansen-osx-x86/build/Lib/test/test_mmap.py, line 706 in test_main File ./Lib/test/regrtest.py, line 1032 in runtest_inner File ./Lib/test/regrtest.py, line 826 in runtest File ./Lib/test/regrtest.py, line 650 in main File ./Lib/test/regrtest.py, line 1607 in module make: *** [buildbottest] Error 1 program finished with exit code 2 elapsedTime=1909.71 - http://www.python.org/dev/buildbot/all/builders/AMD64%20Snow%20Leopard%203.x/builds/46/steps/test/logs/stdio -- components: Tests messages: 133115 nosy: haypo priority: normal severity: normal status: open title: test_mmap timeout (30 min) on AMD64 Snow Leopard 3.x buildbot versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11779 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11779] test_mmap timeout (30 min) on AMD64 Snow Leopard 3.x buildbot
STINNER Victor victor.stin...@haypocalc.com added the comment: The test step was interrupted after 38 mins, 45 secs (including 30 min of timeout) at the test 27, whereas the previous (success) test step took 46 mins, 55 secs to execute all (354) tests. -- nosy: +ixokai ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11779 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11779] test_mmap timeout (30 min) on AMD64 Snow Leopard 3.x buildbot
Steffen Daode Nurpmeso sdao...@googlemail.com added the comment: I can't confirm that. On my cheap MacBook it takes some five minutes: 20:20 ~ $ time python3 -E -Wd -m test -r -w -uall test_mmap Using random seed 1490092 [1/1] test_mmap 1 test OK. [91067 refs] real4m50.301s user0m0.301s sys 0m13.232s ... 20:21 ~ $ ll tmp/test_python_478/ total 6291456 6291456 -rw-r- 1 steffen staff 6442450944 6 Apr 20:21 @test_478_tmp ... Processes: 63 total, 2 running, 2 stuck, 59 sleeping, 251 threads 20:23:00 Load Avg: 0.85, 0.51, 0.24 CPU usage: 9.13% user, 15.38% sys, 75.48% idle SharedLibs: 8260K resident, 9972K data, 0B linkedit. MemRegions: 5563 total, 184M resident, 12M private, 391M shared. PhysMem: 437M wired, 267M active, 113M inactive, 818M used, 1230M free. VM: 140G vsize, 1042M framework vsize, 24419(0) pageins, 0(0) pageouts. Networks: packets: 91/17K in, 101/17K out. Disks: 11128/551M read, 11089/8215M written. PID COMMAND %CPU TIME #TH #WQ #POR #MRE RPRVT RSHRD RSIZE VPRVT VSIZE 478 python3 4.0 00:07.22 2037 137 13M244K 15M30M 2402M ... 20:24 ~ $ ll tmp/test_python_478/ total 5505024 5505024 -rw-r- 1 steffen staff 5637144576 6 Apr 20:24 @test_478_tmp ... Processes: 60 total, 2 running, 1 stuck, 57 sleeping, 246 threads 20:24:00 Load Avg: 1.28, 0.69, 0.33 CPU usage: 8.29% user, 16.9% sys, 75.60% idle SharedLibs: 8260K resident, 9972K data, 0B linkedit. MemRegions: 5444 total, 181M resident, 11M private, 535M shared. PhysMem: 437M wired, 259M active, 124M inactive, 820M used, 1228M free. VM: 133G vsize, 1042M framework vsize, 24421(0) pageins, 0(0) pageouts. Networks: packets: 91/17K in, 101/17K out. Disks: 11128/551M read, 14697/11G written. PID COMMAND %CPU TIME #TH #WQ #POR #MRE RPRVT RSHRD RSIZE VPRVT VSIZE 478 python3 4.4 00:10.04 2037 137 13M244K 15M30M 2402M Is this the bot for which you've tracked those random failures? Maybe this is a hardware failure, then? (In the past i have had problems with my old PC and it's Elitegroup K7S5A motherboard, running on FreeBSD 5.3. That thing randomly produced Stray IRQ 11 (about ~handful a day), and it's ATA controller (i think) randomly caused complete hard disk regions to become unreadable until after a restart.) -- nosy: +sdaoden ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11779 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
