From 669ed45029765df223ba7e9cdc242f62c17497e4 Mon Sep 17 00:00:00 2001 From: Reid Spencer Date: Mon, 9 Jul 2007 08:04:31 +0000 Subject: Subversionify the documentation. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@38442 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/TestingGuide.html | 43 +++++++++++++++++-------------------------- 1 file changed, 17 insertions(+), 26 deletions(-) (limited to 'docs/TestingGuide.html') diff --git a/docs/TestingGuide.html b/docs/TestingGuide.html index 222ccfb52a..cb880373de 100644 --- a/docs/TestingGuide.html +++ b/docs/TestingGuide.html @@ -106,14 +106,14 @@ and tcl.

-

The tests are located in two separate CVS modules. The basic feature and -regression tests are in the main "llvm" module under the directory -llvm/test. A more comprehensive test suite that includes whole -programs in C and C++ is in the llvm-test module. This module should -be checked out to the llvm/projects directory. When you -configure the llvm module, the llvm-test module -will be automatically configured. Alternatively, you can configure the - llvm-test module manually.

+

The tests are located in two separate Subversion modules. The basic feature + and regression tests are in the main "llvm" module under the directory + llvm/test. A more comprehensive test suite that includes whole +programs in C and C++ is in the test-suite module. This module should +be checked out to the llvm/projects directory as llvm-test (for +historical purpose). When you configure the llvm module, +the llvm-test directory will be automatically configured. +Alternatively, you can configure the test-suite module manually.

To run all of the simple tests in LLVM using DejaGNU, use the master Makefile in the llvm/test directory:

@@ -140,7 +140,7 @@ programs), run the llvm-test tests:

 
 
 % cd llvm/projects
-% cvs co llvm-test
+% svn co http://llvm.org/svn/llvm-project/test-suite/trunk llvm-test
 % cd llvm-test
 % ./configure --with-llvmsrc=$LLVM_SRC_ROOT --with-llvmobj=$LLVM_OBJ_ROOT
 % gmake
@@ -201,7 +201,7 @@ a way of benchmarking LLVM performance, both in terms of the efficiency of the
 programs generated as well as the speed with which LLVM compiles, optimizes, and
 generates code.

 
-
All "whole program" tests are located in the llvm-test CVS
+
All "whole program" tests are located in the test-suite Subversion
 module.
@@ -238,8 +238,8 @@ subtrees of the test suite directory tree are as follows:

piece of LLVM assembly language code, often distilled from an actual application or benchmark.

-
  • llvm-test -

    The llvm-test CVS module contains programs that can be compiled +

  • test-suite +

    The test-suite module contains programs that can be compiled with LLVM and executed. These programs are compiled using the native compiler and various LLVM backends. The output from the program compiled with the native compiler is assumed correct; the results from the other programs are @@ -617,8 +617,8 @@ directory to run them.

    1. cd into the llvm/projects directory
      2. -
    2. check out the llvm-test module with:
      - cvs -d :pserver:anon@llvm.org:/var/cvs/llvm co -PR llvm-test
      +
    3. check out the test-suite module with:
      + svn co http://llvm.org/svn/llvm-project/test-suite/trunk llvm-test
      This will get the test suite into llvm/projects/llvm-test
    4. configure the test suite. You can do this one of two ways:
        @@ -760,24 +760,15 @@ as keep track of LLVM's progress over time.

        machine, take a look at the comments at the top of the utils/NewNightlyTest.pl file. If you decide to set up a nightly tester please choose a unique nickname and invoke utils/NewNightlyTest.pl -with the "-nickname [yournickname]" command line option. We usually run it -from a crontab entry that looks like this:

        +with the "-nickname [yournickname]" command line option. -
        -
        -5 3 * * *  $HOME/llvm/utils/NewNightlyTest.pl -parallel -nickname Nickname \
-           $CVSROOT $HOME/buildtest $HOME/cvs/testresults
-
        -
        - -

        Or, you can create a shell script to encapsulate the running of the script. +

        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:

         #!/bin/bash
 BASE=/proj/work/llvm/nightlytest
-export CVSROOT=:pserver:anon@llvm.org:/var/cvs/llvm
 export BUILDDIR=$BASE/build 
 export WEBDIR=$BASE/testresults 
 export LLVMGCCDIR=/proj/work/llvm/cfrontend/install
@@ -786,7 +777,7 @@ 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 2>&1 > output.log
+   -nickname NightlyTester -noexternals > output.log 2>&1
        -- cgit v1.2.3-70-g09d2