summaryrefslogtreecommitdiff
path: root/Lib/test/regrtest.py
diff options
context:
space:
mode:
authorArmin Rigo <arigo@tunes.org>2006-08-09 15:37:26 +0000
committerArmin Rigo <arigo@tunes.org>2006-08-09 15:37:26 +0000
commit97ff04789de3e37af585648de70260a54a29bd47 (patch)
treed992c6d54983772958d2ac9fa7d72ef64b022a0d /Lib/test/regrtest.py
parentc95f7569e875f609ceb7f07d24c09ace9c6111b0 (diff)
downloadcpython-git-97ff04789de3e37af585648de70260a54a29bd47.tar.gz
Concatenation on a long string breaks (SF #1526585).
Diffstat (limited to 'Lib/test/regrtest.py')
-rwxr-xr-xLib/test/regrtest.py4
1 files changed, 3 insertions, 1 deletions
diff --git a/Lib/test/regrtest.py b/Lib/test/regrtest.py
index 26c4d0409f..4553838afc 100755
--- a/Lib/test/regrtest.py
+++ b/Lib/test/regrtest.py
@@ -66,7 +66,9 @@ reports are written to. These parameters all have defaults (5, 4 and
-M runs tests that require an exorbitant amount of memory. These tests
typically try to ascertain containers keep working when containing more than
-2 bilion objects, and only work on 64-bit systems. The passed-in memlimit,
+2 billion objects, which only works on 64-bit systems. There are also some
+tests that try to exhaust the address space of the process, which only makes
+sense on 32-bit systems with at least 2Gb of memory. The passed-in memlimit,
which is a string in the form of '2.5Gb', determines howmuch memory the
tests will limit themselves to (but they may go slightly over.) The number
shouldn't be more memory than the machine has (including swap memory). You