summaryrefslogtreecommitdiffstats
path: root/Lib/test/crashers
diff options
context:
space:
mode:
authorNick Coghlan <ncoghlan@gmail.com>2011-03-16 23:52:14 (GMT)
committerNick Coghlan <ncoghlan@gmail.com>2011-03-16 23:52:14 (GMT)
commitc95ec3d560dd21e678958016aa46313f619b83e7 (patch)
treeea840e87f5324667b97552f3bc62b2c78b466de0 /Lib/test/crashers
parentcfec350e63ee601ce5f777d0780355b06410ccf9 (diff)
downloadcpython-c95ec3d560dd21e678958016aa46313f619b83e7.zip
cpython-c95ec3d560dd21e678958016aa46313f619b83e7.tar.gz
cpython-c95ec3d560dd21e678958016aa46313f619b83e7.tar.bz2
Exercise crashers to ensure they are still covering known error cases
Diffstat (limited to 'Lib/test/crashers')
-rw-r--r--Lib/test/crashers/README4
1 files changed, 4 insertions, 0 deletions
diff --git a/Lib/test/crashers/README b/Lib/test/crashers/README
index 2a73e1b..0259a06 100644
--- a/Lib/test/crashers/README
+++ b/Lib/test/crashers/README
@@ -14,3 +14,7 @@ note if the cause is system or environment dependent and what the variables are.
Once the crash is fixed, the test case should be moved into an appropriate test
(even if it was originally from the test suite). This ensures the regression
doesn't happen again. And if it does, it should be easier to track down.
+
+Also see Lib/test_crashers.py which exercises the crashers in this directory.
+In particular, make sure to add any new infinite loop crashers to the black
+list so it doesn't try to run them.