Stowage/cpython
2
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-10-31 13:41:24 +00:00
Code Issues Projects Releases Packages Wiki Activity

test_compile can be really long if we are using -u compiler.

Browse source 
This may be causing the debian sparc buildbot to fail.
Print a little message to let the user ^w buildbot know it's still thinking.

We may want to adjust the time period which is currently 5 minutes.

Will backport.
This commit is contained in:
Neal Norwitz 2006-04-13 06:34:59 +00:00
parent 412fb67368
commit 07c6071729
1 changed files with 11 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

13
Lib/test/test_compiler.py
View file

@ -1,10 +1,12 @@
import compiler
from compiler.ast import flatten
import os
import os, sys, time, unittest
import test.test_support
import unittest
from random import random
# How much time in seconds can pass before we print a 'Still working' message.
_PRINT_WORKING_MSG_INTERVAL = 5 * 60
class CompilerTest(unittest.TestCase):
def testCompileLibrary(self):
@ -13,11 +15,18 @@ def testCompileLibrary(self):
# that any of the code is correct, merely the compiler is able
# to generate some kind of code for it.
next_time = time.time() + _PRINT_WORKING_MSG_INTERVAL
libdir = os.path.dirname(unittest.__file__)
testdir = os.path.dirname(test.test_support.__file__)
for dir in [libdir, testdir]:
for basename in os.listdir(dir):
# Print still working message since this test can be really slow
if next_time <= time.time():
next_time = time.time() + _PRINT_WORKING_MSG_INTERVAL
print >>sys.__stdout__, \
' testCompileLibrary still working, be patient...'
if not basename.endswith(".py"):
continue
if not TEST_ALL and random() < 0.98: