From: Antoine Pitrou <solipsis@pitrou.net>
Date: Sat, 7 Mar 2009 23:52:26 +0000 (+0000)
Subject: Add notice about strange behaviour of the bigmem tests
X-Git-Tag: v3.1a2~312
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=ec00e2ff45d7068ffee1f0c211fd21d60b08ba21;p=python

Add notice about strange behaviour of the bigmem tests
---

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