summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAlyssa Coghlan <ncoghlan@gmail.com>2024-07-08 05:24:31 (GMT)
committerGitHub <noreply@github.com>2024-07-08 05:24:31 (GMT)
commit59be79ae60073f7b6bdf6ce921560c279937e4ab (patch)
treeecfb7f963d61e873d0f501fb3bd6b0952e63d2df
parentbf74db731bf108e880348f2925160af61570dbf4 (diff)
downloadcpython-59be79ae60073f7b6bdf6ce921560c279937e4ab.zip
cpython-59be79ae60073f7b6bdf6ce921560c279937e4ab.tar.gz
cpython-59be79ae60073f7b6bdf6ce921560c279937e4ab.tar.bz2
gh-108297: Update crashers README for test_crashers removal (#121475)
Update Lib/test/crashers/README for test_crashers removal
-rw-r--r--Lib/test/crashers/README4
1 files changed, 0 insertions, 4 deletions
diff --git a/Lib/test/crashers/README b/Lib/test/crashers/README
index d844385..7111946 100644
--- a/Lib/test/crashers/README
+++ b/Lib/test/crashers/README
@@ -15,7 +15,3 @@ 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.