diff options
author | Neal Norwitz <nnorwitz@gmail.com> | 2006-04-14 06:35:46 (GMT) |
---|---|---|
committer | Neal Norwitz <nnorwitz@gmail.com> | 2006-04-14 06:35:46 (GMT) |
commit | 38a76a101796d43fb8cd6c6d5ba54bb811d06f49 (patch) | |
tree | da15427e10dc857dec98bf9366d302e2a6ffa571 | |
parent | 621292237c2d47dabb33b37ec6db945fa1d5716e (diff) | |
download | cpython-38a76a101796d43fb8cd6c6d5ba54bb811d06f49.zip cpython-38a76a101796d43fb8cd6c6d5ba54bb811d06f49.tar.gz cpython-38a76a101796d43fb8cd6c6d5ba54bb811d06f49.tar.bz2 |
Copy note from leakers README here too. We want to keep all test cases.
-rw-r--r-- | Lib/test/crashers/README | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/Lib/test/crashers/README b/Lib/test/crashers/README index 9369282..070c3f1 100644 --- a/Lib/test/crashers/README +++ b/Lib/test/crashers/README @@ -13,3 +13,8 @@ Each test should have a link to the bug report: Put as much info into a docstring or comments to help determine the cause of the failure. Particularly 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. |