From 5da60ba6aa759c7b5ed366d3767c08b4939e7856 Mon Sep 17 00:00:00 2001 From: Misha Brukman Date: Thu, 10 Mar 2005 22:51:59 +0000 Subject: [PATCH] * Add directions to send output of nightly test script to llvm-testresults@cs * Use the doc_code class to nightly test script example * Enclose file names in tags * Achieve compliance with HTML-4.01 Strict llvm-svn: 20556 --- llvm/docs/TestingGuide.html | 40 +++++++++++++++++++++---------------- 1 file changed, 23 insertions(+), 17 deletions(-) diff --git a/llvm/docs/TestingGuide.html b/llvm/docs/TestingGuide.html index 467e58ec1bb0..ced17745def3 100644 --- a/llvm/docs/TestingGuide.html +++ b/llvm/docs/TestingGuide.html @@ -116,7 +116,9 @@ or
 % gmake -C llvm/test TESTSUITE=Regression/Transforms
-
Note: If you are running the tests with objdir != subdir you must have run the complete testsuite before you can specify a subdirectory.
+ +

Note: If you are running the tests with objdir != subdir you must +have run the complete testsuite before you can specify a subdirectory.

To run the comprehensive test suite (tests that compile and execute whole programs), run the llvm-test tests:

@@ -284,7 +286,8 @@ file:

There are a couple patterns within a RUN line that the llvm-runtest procedure looks for and replaces with the appropriate syntax:

- +

There are also several scripts in the llvm/test/Scripts directory that you might find useful when writing RUN lines.

@@ -467,18 +470,21 @@ program test (described above), run all of the feature and regression tests, and then delete the checked out tree. This tester is designed to ensure that programs don't break as well as keep track of LLVM's progress over time.

-

-If you'd like to set up an instance of the nightly tester to run on your -machine, take a look at the comments at the top of the utils/NightlyTester.pl -file. We usually run it from a crontab entry that looks ilke this: -

+

If you'd like to set up an instance of the nightly tester to run on your +machine, take a look at the comments at the top of the +utils/NightlyTester.pl file. We usually run it from a crontab entry +that looks ilke this:

+
-5 3 * * *  $HOME/llvm/utils/NightlyTest.pl -parallel -enable-linscan ...CVSREPOSTORY... $HOME/buildtest-X86 $HOME/cvs/testresults-X86
+5 3 * * *  $HOME/llvm/utils/NightlyTest.pl -parallel $CVSROOT $HOME/buildtest-X86 $HOME/cvs/testresults-X86
+

Or, you can create a shell script to encapsulate the running of the script. -The optimized x86 Linux nightly test is run from just such a script: +The optimized x86 Linux nightly test is run from just such a script:

+ +
 #!/bin/bash
 BASE=/proj/work/llvm/nightlytest
@@ -490,15 +496,15 @@ export PATH=/proj/install/bin:$LLVMGCCDIR/bin:$PATH
 export LD_LIBRARY_PATH=/proj/install/lib
 cd $BASE
 cp /proj/work/llvm/llvm/utils/NightlyTest.pl .
-nice ./NightlyTest.pl -nice -release -verbose -parallel -enable-linscan -noexternals
+nice ./NightlyTest.pl -nice -release -verbose -parallel -enable-linscan -noexternals 2>&1 > output.log
+mail -s 'X86 nightly tester results' llvm-testresults@cs.uiuc.edu < output.log
+
+ +

Take a look at the NightlyTest.pl file to see what all of the flags +and strings do. If you start running the nightly tests, please let us know and +we'll link your page to the global tester page. Thanks!

-

-Take a look at the NightlyTest.pl file to see what all of the flags and -strings do. If you start running the nightly tests, please let us know and -we'll link your page to the global tester page. Thanks! -

-