summaryrefslogtreecommitdiffstats
path: root/llvm/docs/TestSuiteMakefileGuide.html
diff options
context:
space:
mode:
Diffstat (limited to 'llvm/docs/TestSuiteMakefileGuide.html')
-rw-r--r--llvm/docs/TestSuiteMakefileGuide.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/llvm/docs/TestSuiteMakefileGuide.html b/llvm/docs/TestSuiteMakefileGuide.html
index 0a644d2813d..1b24250380f 100644
--- a/llvm/docs/TestSuiteMakefileGuide.html
+++ b/llvm/docs/TestSuiteMakefileGuide.html
@@ -238,12 +238,12 @@ LLVM.</p>
simple one is simply running <tt>gmake</tt> with no arguments. This will
compile and run all programs in the tree using a number of different methods
and compare results. Any failures are reported in the output, but are likely
- drowned in the other output. Passes are not reported explicitely.</p>
+ drowned in the other output. Passes are not reported explicitly.</p>
<p>Somewhat better is running <tt>gmake TEST=sometest test</tt>, which runs
the specified test and usually adds per-program summaries to the output
(depending on which sometest you use). For example, the <tt>nightly</tt> test
- explicitely outputs TEST-PASS or TEST-FAIL for every test after each program.
+ explicitly outputs TEST-PASS or TEST-FAIL for every test after each program.
Though these lines are still drowned in the output, it's easy to grep the
output logs in the Output directories.</p>
OpenPOWER on IntegriCloud