diff options
| -rw-r--r-- | Lib/test/crashers/compiler_recursion.py | 4 | ||||
| -rw-r--r-- | Lib/test/test_crashers.py | 2 |
2 files changed, 4 insertions, 2 deletions
diff --git a/Lib/test/crashers/compiler_recursion.py b/Lib/test/crashers/compiler_recursion.py index 8fd93fc..c00cd6e 100644 --- a/Lib/test/crashers/compiler_recursion.py +++ b/Lib/test/crashers/compiler_recursion.py @@ -9,5 +9,5 @@ Recorded on the tracker as http://bugs.python.org/issue11383 # e.g. '1*'*10**5+'1' will die in compiler_visit_expr # The exact limit to destroy the stack will vary by platform -# but 100k should do the trick most places -compile('()'*10**5, '?', 'exec') +# but 1M should do the trick most places +compile('()'*10**6, '?', 'exec') diff --git a/Lib/test/test_crashers.py b/Lib/test/test_crashers.py index ee612c2..86f88f7 100644 --- a/Lib/test/test_crashers.py +++ b/Lib/test/test_crashers.py @@ -24,6 +24,8 @@ class CrasherTest(unittest.TestCase): continue # Some "crashers" only trigger an exception rather than a # segfault. Consider that an acceptable outcome. + if test.support.verbose: + print("Checking crasher:", fname) assert_python_failure(fname) |