[Python-checkins] [3.6] bpo-31201: Clarify command to re-run failing test(s) with example (GH-6417) (GH-6438)
Ned Deily
webhook-mailer at python.org
Mon Apr 9 17:19:35 EDT 2018
https://github.com/python/cpython/commit/83bb39907ec3828aec6d99bb9338283bd6b30ac2
commit: 83bb39907ec3828aec6d99bb9338283bd6b30ac2
branch: 3.6
author: Miss Islington (bot) <31488909+miss-islington at users.noreply.github.com>
committer: Ned Deily <nad at python.org>
date: 2018-04-09T17:19:32-04:00
summary:
[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 <aaronang at users.noreply.github.com>
files:
M README.rst
diff --git a/README.rst b/README.rst
index 75be9f7628f8..6ef60a1f6627 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 <https://bugs.python.org>`_ and
More information about the Python-checkins
mailing list