diff options
author | Aaron Ang <aaronang@users.noreply.github.com> | 2018-04-09 21:09:31 (GMT) |
---|---|---|
committer | Ned Deily <nad@python.org> | 2018-04-09 21:09:31 (GMT) |
commit | 0f914b5b5f6ba186afd7112fc851c97247076f70 (patch) | |
tree | a82eeafc219a094d155e1a4ab61cd96ab085ac09 | |
parent | c93938b5beea4c3f592119ebee6d4029558db8de (diff) | |
download | cpython-0f914b5b5f6ba186afd7112fc851c97247076f70.zip cpython-0f914b5b5f6ba186afd7112fc851c97247076f70.tar.gz cpython-0f914b5b5f6ba186afd7112fc851c97247076f70.tar.bz2 |
bpo-31201: Clarify command to re-run failing test(s) with example (GH-6417)
-rw-r--r-- | README.rst | 5 |
1 files changed, 3 insertions, 2 deletions
@@ -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 <https://bugs.python.org>`_ and |