diff options
| author | Neal Norwitz <nnorwitz@gmail.com> | 2006-04-17 01:49:14 (GMT) |
|---|---|---|
| committer | Neal Norwitz <nnorwitz@gmail.com> | 2006-04-17 01:49:14 (GMT) |
| commit | 7ebd1f8491f553bd599eacdd60276dbc2f126789 (patch) | |
| tree | d3833971fb4c2e42dd13eda4604e005b0e79ba42 /Misc | |
| parent | 0f77da36e9a44b80f2a5d828602f4bbadad1a233 (diff) | |
| download | cpython-7ebd1f8491f553bd599eacdd60276dbc2f126789.zip cpython-7ebd1f8491f553bd599eacdd60276dbc2f126789.tar.gz cpython-7ebd1f8491f553bd599eacdd60276dbc2f126789.tar.bz2 | |
Add some notes about a couple of poorly behaved tests
Diffstat (limited to 'Misc')
| -rw-r--r-- | Misc/README.valgrind | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/Misc/README.valgrind b/Misc/README.valgrind index 157bdc3..b5a9a32 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: -------- |