Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(136)

Unified Diff: third_party/coverage-3.7.1/doc/config.rst

Issue 225633007: Upgrade to coverage 3.7.1 and have it auto-build itself on first use. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/tools/build
Patch Set: sigh our imports are a mess Created 6 years, 9 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « third_party/coverage-3.7.1/doc/cmd.rst ('k') | third_party/coverage-3.7.1/doc/contributing.rst » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: third_party/coverage-3.7.1/doc/config.rst
diff --git a/third_party/coverage-3.6/doc/config.rst b/third_party/coverage-3.7.1/doc/config.rst
similarity index 87%
rename from third_party/coverage-3.6/doc/config.rst
rename to third_party/coverage-3.7.1/doc/config.rst
index f6d8f1fce1ad62a0152167d93849688372cafc07..7ff820217168add21d4bdf723c236ac1a6f4395d 100644
--- a/third_party/coverage-3.6/doc/config.rst
+++ b/third_party/coverage-3.7.1/doc/config.rst
@@ -9,6 +9,7 @@ Configuration files
:history: 20100824T092900, added ``precision``.
:history: 20110604T184400, updated for 3.5.
:history: 20110827T212700, updated for 3.5.1
+:history: 20130926T222300, updated for 3.6.1
Coverage.py options can be specified in a configuration file. This makes it
@@ -21,9 +22,9 @@ sub-processes. See :ref:`subprocess` for more details.
The default name for configuration files is ``.coveragerc``, in the same
directory coverage.py is being run in. Most of the settings in the
-configuration file are tied to your source code and how it should be
-measured, so it should be stored with your source, and checked into
-source control, rather than put in your home directory.
+configuration file are tied to your source code and how it should be measured,
+so it should be stored with your source, and checked into source control,
+rather than put in your home directory.
Syntax
@@ -92,6 +93,9 @@ standard library.
``data_file`` (string, default ".coverage"): the name of the data file to use
for storing or reporting coverage.
+``debug`` (multi-string): a list of debug options. See :ref:`the run
+--debug option <cmd_run_debug>` for details.
+
``include`` (multi-string): a list of filename patterns, the files to include
in measurement or reporting. See :ref:`source` for details.
@@ -114,8 +118,8 @@ Try this if you get seemingly impossible results.
[paths]
-------
-The entries in this section are lists of file paths that should be
-considered equivalent when combining data from different machines::
+The entries in this section are lists of file paths that should be considered
+equivalent when combining data from different machines::
[paths]
source =
@@ -123,15 +127,15 @@ considered equivalent when combining data from different machines::
/jenkins/build/*/src
c:\myproj\src
-The names of the entries are ignored, you may choose any name that
-you like. The value is a lists of strings. When combining data
-with the ``combine`` command, two file paths will be combined
-if they start with paths from the same list.
+The names of the entries are ignored, you may choose any name that you like.
+The value is a lists of strings. When combining data with the ``combine``
+command, two file paths will be combined if they start with paths from the same
+list.
-The first value must be an actual file path on the machine where
-the reporting will happen, so that source code can be found.
-The other values can be file patterns to match against the paths
-of collected data.
+The first value must be an actual file path on the machine where the reporting
+will happen, so that source code can be found. The other values can be file
+patterns to match against the paths of collected data, or they can be absolute
+or relative file paths on the current machine.
See :ref:`cmd_combining` for more information.
@@ -163,11 +167,11 @@ you are replacing all the partial branch regexes so you'll need to also
supply the "pragma: no branch" regex if you still want to use it.
``precision`` (integer): the number of digits after the decimal point to
-display for reported coverage percentages. The default is 0, displaying
-for example "87%". A value of 2 will display percentages like "87.32%".
+display for reported coverage percentages. The default is 0, displaying for
+example "87%". A value of 2 will display percentages like "87.32%".
-``show_missing`` (boolean, default False): when running a summary report,
-show missing lines. See :ref:`cmd_summary` for more information.
+``show_missing`` (boolean, default False): when running a summary report, show
+missing lines. See :ref:`cmd_summary` for more information.
.. _config_html:
« no previous file with comments | « third_party/coverage-3.7.1/doc/cmd.rst ('k') | third_party/coverage-3.7.1/doc/contributing.rst » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698