From 9d07f9486313e3bbd70b6b9a3dd1f0744ea835ee Mon Sep 17 00:00:00 2001 From: Eli Bendersky Date: Tue, 20 Nov 2012 00:26:08 +0000 Subject: ReST-ify some markup in the LIT document llvm-svn: 168345 --- llvm/docs/CommandGuide/lit.rst | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) (limited to 'llvm/docs/CommandGuide') 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 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:: -: () + : () where 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 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:: - TEST '()' -... log message ... - + TEST '()' + ... log message ... + where should be the name of a preceding reported test, is a string of '\*' characters *at least* four characters long (the -- cgit v1.2.3