llvm.org GIT mirror llvm / fc1a27b
* 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 <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 Misha Brukman 14 years ago
1 changed file(s) with 28 addition(s) and 22 deletion(s). Raw diff Collapse all Expand all
115115

                  
                
116116 % gmake -C llvm/test TESTSUITE=Regression/Transforms
117117
118
Note: If you are running the tests with objdir != subdir you must have run the complete testsuite before you can specify a subdirectory.
118
119

Note: If you are running the tests with objdir != subdir you must

120 have run the complete testsuite before you can specify a subdirectory.

119121
120122

To run the comprehensive test suite (tests that compile and execute whole

121123 programs), run the llvm-test tests:

283285

There are a couple patterns within a RUN line that the

284286 llvm-runtest procedure looks for and replaces with the appropriate
285287 syntax:

286
288
289
287290
%p
288291
The path to the source directory. This is for locating
289292 any supporting files that are not generated by the test, but used by
303306
304307
%llvmgcc
Full path to the llvm-gcc executable.
305308
%llvmgxx
Full path to the llvm-g++ executable.
306 ul>
309 dl>
307310
308311

There are also several scripts in the llvm/test/Scripts directory

309312 that you might find useful when writing RUN lines.

466469 and then delete the checked out tree. This tester is designed to ensure that
467470 programs don't break as well as keep track of LLVM's progress over time.

468471
469

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

474
475

                  
                
476 5 3 * * * $HOME/llvm/utils/NightlyTest.pl -parallel -enable-linscan ...CVSREPOSTORY... $HOME/buildtest-X86 $HOME/cvs/testresults-X86
477 </pre>
472 <p>If you'd like to set up an instance of the nightly tester to run on your
473 machine, take a look at the comments at the top of the
474 utils/NightlyTester.pl file. We usually run it from a crontab entry
475 that looks ilke this:

476
477
478

                  
                
479 5 3 * * * $HOME/llvm/utils/NightlyTest.pl -parallel $CVSROOT $HOME/buildtest-X86 $HOME/cvs/testresults-X86
480
481
478482
479483

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

480 The optimized x86 Linux nightly test is run from just such a script:
484 The optimized x86 Linux nightly test is run from just such a script:

485
486
481487

                  
                
482488 #!/bin/bash
483489 BASE=/proj/work/llvm/nightlytest
489495 export LD_LIBRARY_PATH=/proj/install/lib
490496 cd $BASE
491497 cp /proj/work/llvm/llvm/utils/NightlyTest.pl .
492 nice ./NightlyTest.pl -nice -release -verbose -parallel -enable-linscan -noexternals
493
494
495

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

500
498 nice ./NightlyTest.pl -nice -release -verbose -parallel -enable-linscan -noexternals 2>&1 > output.log
499 mail -s 'X86 nightly tester results' llvm-testresults@cs.uiuc.edu < output.log
500
501
502
503

Take a look at the NightlyTest.pl file to see what all of the flags

504 and strings do. If you start running the nightly tests, please let us know and
505 we'll link your page to the global tester page. Thanks!

506
501507
502508
503509