mirror of
https://github.com/RPCS3/llvm.git
synced 2024-11-25 12:49:50 +00:00
docs/TestingGuide: Rip out description of old nightly tester infrastructure. The
official recommendation is to use LNT instead. I will write docs on setting up an LNT installation for submission to llvm.org, one day. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@110004 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
parent
e3536b89b4
commit
1628665065
@ -43,7 +43,6 @@
|
||||
<li><a href="#testsuitecustom">Writing custom tests for llvm-test</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#nightly">Running the nightly tester</a></li>
|
||||
</ol>
|
||||
|
||||
<div class="doc_author">
|
||||
@ -1135,66 +1134,6 @@ example reports that can do fancy stuff.</p>
|
||||
|
||||
</div>
|
||||
|
||||
<!--=========================================================================-->
|
||||
<div class="doc_section"><a name="nightly">Running the nightly tester</a></div>
|
||||
<!--=========================================================================-->
|
||||
|
||||
<div class="doc_text">
|
||||
|
||||
<p>
|
||||
The <a href="http://llvm.org/nightlytest/">LLVM Nightly Testers</a>
|
||||
automatically check out an LLVM tree, build it, run the "nightly"
|
||||
program test (described above), run all of the DejaGNU tests,
|
||||
delete the checked out tree, and then submit the results to
|
||||
<a href="http://llvm.org/nightlytest/">http://llvm.org/nightlytest/</a>.
|
||||
After test results are submitted to
|
||||
<a href="http://llvm.org/nightlytest/">http://llvm.org/nightlytest/</a>,
|
||||
they are processed and displayed on the tests page. An email to
|
||||
<a href="http://lists.cs.uiuc.edu/pipermail/llvm-testresults/">
|
||||
llvm-testresults@cs.uiuc.edu</a> summarizing the results is also generated.
|
||||
This testing scheme is designed to ensure that programs don't break as well
|
||||
as keep track of LLVM's progress over time.</p>
|
||||
|
||||
<p>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
|
||||
<tt>utils/NewNightlyTest.pl</tt> file. If you decide to set up a nightly tester
|
||||
please choose a unique nickname and invoke <tt>utils/NewNightlyTest.pl</tt>
|
||||
with the "-nickname [yournickname]" command line option.
|
||||
|
||||
<p>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:</p>
|
||||
|
||||
<div class="doc_code">
|
||||
<pre>
|
||||
#!/bin/bash
|
||||
BASE=/proj/work/llvm/nightlytest
|
||||
export BUILDDIR=$BASE/build
|
||||
export WEBDIR=$BASE/testresults
|
||||
export LLVMGCCDIR=/proj/work/llvm/cfrontend/install
|
||||
export PATH=/proj/install/bin:$LLVMGCCDIR/bin:$PATH
|
||||
export LD_LIBRARY_PATH=/proj/install/lib
|
||||
cd $BASE
|
||||
cp /proj/work/llvm/llvm/utils/NewNightlyTest.pl .
|
||||
nice ./NewNightlyTest.pl -nice -release -verbose -parallel -enable-linscan \
|
||||
-nickname NightlyTester -noexternals > output.log 2>&1
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
<p>It is also possible to specify the the location your nightly test results
|
||||
are submitted. You can do this by passing the command line option
|
||||
"-submit-server [server_address]" and "-submit-script [script_on_server]" to
|
||||
<tt>utils/NewNightlyTest.pl</tt>. For example, to submit to the llvm.org
|
||||
nightly test results page, you would invoke the nightly test script with
|
||||
"-submit-server llvm.org -submit-script /nightlytest/NightlyTestAccept.cgi".
|
||||
If these options are not specified, the nightly test script sends the results
|
||||
to the llvm.org nightly test results page.</p>
|
||||
|
||||
<p>Take a look at the <tt>NewNightlyTest.pl</tt> file to see what all of the
|
||||
flags and strings do. If you start running the nightly tests, please let us
|
||||
know. Thanks!</p>
|
||||
|
||||
</div>
|
||||
|
||||
<!-- *********************************************************************** -->
|
||||
|
||||
<hr>
|
||||
|
Loading…
Reference in New Issue
Block a user