summaryrefslogtreecommitdiff
path: root/Misc/README.valgrind
diff options
context:
space:
mode:
authorThomas Wouters <thomas@python.org>2006-04-21 10:40:58 +0000
committerThomas Wouters <thomas@python.org>2006-04-21 10:40:58 +0000
commit49fd7fa4431da299196d74087df4a04f99f9c46f (patch)
tree35ace5fe78d3d52c7a9ab356ab9f6dbf8d4b71f4 /Misc/README.valgrind
parent9ada3d6e29d5165dadacbe6be07bcd35cfbef59d (diff)
downloadcpython-git-49fd7fa4431da299196d74087df4a04f99f9c46f.tar.gz
Merge p3yk branch with the trunk up to revision 45595. This breaks a fair
number of tests, all because of the codecs/_multibytecodecs issue described here (it's not a Py3K issue, just something Py3K discovers): http://mail.python.org/pipermail/python-dev/2006-April/064051.html Hye-Shik Chang promised to look for a fix, so no need to fix it here. The tests that are expected to break are: test_codecencodings_cn test_codecencodings_hk test_codecencodings_jp test_codecencodings_kr test_codecencodings_tw test_codecs test_multibytecodec This merge fixes an actual test failure (test_weakref) in this branch, though, so I believe merging is the right thing to do anyway.
Diffstat (limited to 'Misc/README.valgrind')
-rw-r--r--Misc/README.valgrind6
1 files changed, 6 insertions, 0 deletions
diff --git a/Misc/README.valgrind b/Misc/README.valgrind
index 157bdc3ca3..b5a9a32e1d 100644
--- a/Misc/README.valgrind
+++ b/Misc/README.valgrind
@@ -24,6 +24,12 @@ You may need to run the tests in batches under Valgrind to keep
the memory usage down to allow the tests to complete. It seems to take
about 5 times longer to run --without-pymalloc.
+Apr 15, 2006:
+ test_ctypes causes Valgrind 3.1.1 to fail (crash).
+ test_socket_ssl should be skipped when running valgrind.
+ The reason is that it purposely uses uninitialized memory.
+ This causes many spurious warnings, so it's easier to just skip it.
+
Details:
--------