summaryrefslogtreecommitdiff
path: root/Lib/test/test_bigmem.py
diff options
context:
space:
mode:
authorAntoine Pitrou <solipsis@pitrou.net>2009-03-07 23:52:26 +0000
committerAntoine Pitrou <solipsis@pitrou.net>2009-03-07 23:52:26 +0000
commitec00e2ff45d7068ffee1f0c211fd21d60b08ba21 (patch)
tree396a89eaf6ef162b020ad1aaa5b818d80b9f0808 /Lib/test/test_bigmem.py
parent7cdb495e90370641f83e70d31d53c4c994672bc2 (diff)
downloadcpython-git-ec00e2ff45d7068ffee1f0c211fd21d60b08ba21.tar.gz
Add notice about strange behaviour of the bigmem tests
Diffstat (limited to 'Lib/test/test_bigmem.py')
-rw-r--r--Lib/test/test_bigmem.py4
1 files changed, 4 insertions, 0 deletions
diff --git a/Lib/test/test_bigmem.py b/Lib/test/test_bigmem.py
index 254c21d6f6..7896748fe8 100644
--- a/Lib/test/test_bigmem.py
+++ b/Lib/test/test_bigmem.py
@@ -33,6 +33,10 @@ import functools
# memuse-per-size should remain sane (less than a few thousand); if your
# test uses more, adjust 'size' upward, instead.
+# BEWARE: it seems that one failing test can yield other subsequent tests to
+# fail as well. I do not know whether it is due to memory fragmentation
+# issues, or other specifics of the platform malloc() routine.
+
character_size = 4 if sys.maxunicode > 0xFFFF else 2