From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Mon, 9 Apr 2018 21:19:32 +0000 (-0700) Subject: [3.6] bpo-31201: Clarify command to re-run failing test(s) with example (GH-6417... X-Git-Tag: v3.6.6rc1~187 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=83bb39907ec3828aec6d99bb9338283bd6b30ac2;p=python [3.6] bpo-31201: Clarify command to re-run failing test(s) with example (GH-6417) (GH-6438) (cherry picked from commit 0f914b5b5f6ba186afd7112fc851c97247076f70) Co-authored-by: Aaron Ang --- diff --git a/README.rst b/README.rst index 75be9f7628..6ef60a1f66 100644 --- a/README.rst +++ b/README.rst @@ -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 `_ and