]> granicus.if.org Git - python/commitdiff
[3.6] bpo-31201: Clarify command to re-run failing test(s) with example (GH-6417...
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Mon, 9 Apr 2018 21:19:32 +0000 (14:19 -0700)
committerNed Deily <nad@python.org>
Mon, 9 Apr 2018 21:19:32 +0000 (17:19 -0400)
(cherry picked from commit 0f914b5b5f6ba186afd7112fc851c97247076f70)

Co-authored-by: Aaron Ang <aaronang@users.noreply.github.com>
README.rst

index 75be9f7628f85876229cee4de50b83f3bf382882..6ef60a1f6627fcde4c1b7aadd35d4747bb3bd999 100644 (file)
@@ -171,9 +171,10 @@ something is wrong.
 By default, tests are prevented from overusing resources like disk space and
 memory.  To enable these tests, run ``make testall``.
 
-If any tests fail, you can re-run the failing test(s) in verbose mode::
+If any tests fail, you can re-run the failing test(s) in verbose mode.  For
+example, if ``test_os`` and ``test_gdb`` failed, you can run::
 
-    make test TESTOPTS="-v test_that_failed"
+    make test TESTOPTS="-v test_os test_gdb"
 
 If the failure persists and appears to be a problem with Python rather than
 your environment, you can `file a bug report <https://bugs.python.org>`_ and