diff options
| author | Eli Bendersky <eliben@google.com> | 2012-11-20 00:26:08 +0000 |
|---|---|---|
| committer | Eli Bendersky <eliben@google.com> | 2012-11-20 00:26:08 +0000 |
| commit | 9d07f9486313e3bbd70b6b9a3dd1f0744ea835ee (patch) | |
| tree | 38394efe56c6ae0e519f0008211ca079472f15c9 | |
| parent | b1d992fb358a390a64e0e9578520f5d9b9a0d261 (diff) | |
| download | bcm5719-llvm-9d07f9486313e3bbd70b6b9a3dd1f0744ea835ee.tar.gz bcm5719-llvm-9d07f9486313e3bbd70b6b9a3dd1f0744ea835ee.zip | |
ReST-ify some markup in the LIT document
llvm-svn: 168345
| -rw-r--r-- | llvm/docs/CommandGuide/lit.rst | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/llvm/docs/CommandGuide/lit.rst b/llvm/docs/CommandGuide/lit.rst index 9e96cd2a4bf..8886fe6a45f 100644 --- a/llvm/docs/CommandGuide/lit.rst +++ b/llvm/docs/CommandGuide/lit.rst @@ -430,14 +430,14 @@ TEST RUN OUTPUT FORMAT ~~~~~~~~~~~~~~~~~~~~~~ -The b<lit> output for a test run conforms to the following schema, in both short -and verbose modes (although in short mode no PASS lines will be shown). This -schema has been chosen to be relatively easy to reliably parse by a machine (for -example in buildbot log scraping), and for other tools to generate. +The **lit** output for a test run conforms to the following schema, in both +short and verbose modes (although in short mode no PASS lines will be shown). +This schema has been chosen to be relatively easy to reliably parse by a machine +(for example in buildbot log scraping), and for other tools to generate. -Each test result is expected to appear on a line that matches: +Each test result is expected to appear on a line that matches:: -<result code>: <test name> (<progress info>) + <result code>: <test name> (<progress info>) where <result-code> is a standard test result such as PASS, FAIL, XFAIL, XPASS, UNRESOLVED, or UNSUPPORTED. The performance result codes of IMPROVED and @@ -449,11 +449,11 @@ The <progress info> field can be used to report progress information such as (1/300) or can be empty, but even when empty the parentheses are required. Each test result may include additional (multiline) log information in the -following format. +following format:: -<log delineator> TEST '(<test name>)' <trailing delineator> -... log message ... -<log delineator> + <log delineator> TEST '(<test name>)' <trailing delineator> + ... log message ... + <log delineator> where <test name> should be the name of a preceding reported test, <log delineator> is a string of '\*' characters *at least* four characters long (the |
