6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2025-02-04 07:32:13 +00:00
Code Issues Projects Releases Wiki Activity

* Add directions to send output of nightly test script to llvm-testresults@cs

Browse Source 
* Use the doc_code class to nightly test script example
* Enclose file names in <tt> tags
* Achieve compliance with HTML-4.01 Strict


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@20556 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Misha Brukman 2005-03-10 22:51:59 +00:00
parent e97568c3c4
commit fc1a27b2a5
1 changed files with 23 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

40
docs/TestingGuide.html
View File

@ -116,7 +116,9 @@ or<br>
<pre> <pre>
% gmake -C llvm/test TESTSUITE=Regression/Transforms % gmake -C llvm/test TESTSUITE=Regression/Transforms
</pre> </pre>
<dd><b>Note: If you are running the tests with <tt>objdir != subdir</tt> you must have run the complete testsuite before you can specify a subdirectory.</b></dd>
<p><b>Note: If you are running the tests with <tt>objdir != subdir</tt> you must
have run the complete testsuite before you can specify a subdirectory.</b></p>
<p>To run the comprehensive test suite (tests that compile and execute whole <p>To run the comprehensive test suite (tests that compile and execute whole
programs), run the <tt>llvm-test</tt> tests:</p> programs), run the <tt>llvm-test</tt> tests:</p>
@ -284,7 +286,8 @@ file:</p>
<p>There are a couple patterns within a <tt>RUN</tt> line that the <p>There are a couple patterns within a <tt>RUN</tt> line that the
llvm-runtest procedure looks for and replaces with the appropriate llvm-runtest procedure looks for and replaces with the appropriate
syntax:</p> syntax:</p>
<ul>
<dl style="margin-left: 25px">
<dt>%p</dt> <dt>%p</dt>
<dd>The path to the source directory. This is for locating <dd>The path to the source directory. This is for locating
any supporting files that are not generated by the test, but used by any supporting files that are not generated by the test, but used by
@ -304,7 +307,7 @@ platforms support grep -C.</dd>
<dt>%llvmgcc</dt> <dd>Full path to the llvm-gcc executable.</dd> <dt>%llvmgcc</dt> <dd>Full path to the llvm-gcc executable.</dd>
<dt>%llvmgxx</dt> <dd>Full path to the llvm-g++ executable.</dd> <dt>%llvmgxx</dt> <dd>Full path to the llvm-g++ executable.</dd>
</ul> </dl>
<p>There are also several scripts in the llvm/test/Scripts directory <p>There are also several scripts in the llvm/test/Scripts directory
that you might find useful when writing <tt>RUN</tt> lines.</p> that you might find useful when writing <tt>RUN</tt> lines.</p>
@ -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 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.</p> programs don't break as well as keep track of LLVM's progress over time.</p>
<p> <p>If you'd like to set up an instance of the nightly tester to run on your
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
machine, take a look at the comments at the top of the utils/NightlyTester.pl <tt>utils/NightlyTester.pl</tt> file. We usually run it from a crontab entry
file. We usually run it from a crontab entry that looks ilke this: that looks ilke this:</p>
</p>
<div class="doc_code">
<pre> <pre>
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
</pre> </pre>
</div>
<p>Or, you can create a shell script to encapsulate the running of the script. <p>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:</p>
<div class="doc_code">
<pre> <pre>
#!/bin/bash #!/bin/bash
BASE=/proj/work/llvm/nightlytest BASE=/proj/work/llvm/nightlytest
@ -490,15 +496,15 @@ export PATH=/proj/install/bin:$LLVMGCCDIR/bin:$PATH
export LD_LIBRARY_PATH=/proj/install/lib export LD_LIBRARY_PATH=/proj/install/lib
cd $BASE cd $BASE
cp /proj/work/llvm/llvm/utils/NightlyTest.pl . 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&gt;&amp;1 &gt; output.log
mail -s 'X86 nightly tester results' <a href="http://mail.cs.uiuc.edu/mailman/listinfo/llvm-testresults">llvm-testresults@cs.uiuc.edu</a> &lt; output.log
</pre> </pre>
</div>
<p>Take a look at the <tt>NightlyTest.pl</tt> 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!</p>
<p>
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!
</p>
</div> </div>
<!-- *********************************************************************** --> <!-- *********************************************************************** -->