From 71a3837bf39580ffa828c14247230a9277b9d5b1 Mon Sep 17 00:00:00 2001 From: "Miss Islington (bot)" <31488909+miss-islington@users.noreply.github.com> Date: Mon, 9 Apr 2018 14:17:20 -0700 Subject: [3.7] bpo-31201: Clarify command to re-run failing test(s) with example (GH-6417) (GH-6437) (cherry picked from commit 0f914b5b5f6ba186afd7112fc851c97247076f70) Co-authored-by: Aaron Ang --- README.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'README.rst') diff --git a/README.rst b/README.rst index a795bfece8..607f2613a0 100644 --- a/README.rst +++ b/README.rst @@ -172,9 +172,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 -- cgit v1.2.1