From 89b6f2ea9fdba7e99820bed7ecbbfedd549c9a10 Mon Sep 17 00:00:00 2001 From: Daniel Dunbar Date: Thu, 3 Nov 2011 21:03:53 +0000 Subject: utils: Remove (way) old nightly test scripts, I don't think anyone uses them and LNT has way better tools than this. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@143655 91177308-0d34-0410-b5e6-96231b3b80d8 --- utils/NightlyTestTemplate.html | 244 ----------------------------------------- 1 file changed, 244 deletions(-) delete mode 100644 utils/NightlyTestTemplate.html (limited to 'utils/NightlyTestTemplate.html') diff --git a/utils/NightlyTestTemplate.html b/utils/NightlyTestTemplate.html deleted file mode 100644 index c38bb2e776..0000000000 --- a/utils/NightlyTestTemplate.html +++ /dev/null @@ -1,244 +0,0 @@ - -LLVM Test Results for $DateString - - -
LLVM Test Results for $DateString
-
- - -
- -
-
-Sections:
-
-Overview
-Changes
-Dejagnu Tests
-Trends
-Programs
-
- -

-
-
Previous:
-
- $PrevDaysList -
-

- -Back to:
-Test Results
-LLVM Page

- -

 - -
-
-
Today's Test Results Overview -

- - - - - -
- -
Lines Of Code over Time
-Click for larger view -
- -

Nightly Test Overview:

-
    -
  • Start: $TestStartTime
    • -
  • Finish: $TestFinishTime
    • -
  • Platform: $TestPlatform
    • -
-

CVS Tree Overview:

-
    -
  • CVS Checkout Log -
      - $NumDirsInCVS dirs, $NumFilesInCVS files, $LOC - lines of code, checked out in $CVSCheckoutTime seconds
    -
  • Compilation Log - - - - - -
    ItemCPU TimeWall Clock
    Configure CVS Tree$ConfigTime$ConfigWallTime
    Build CVS Tree$BuildTime$BuildWallTime
    Run Dejagnu Tests$DejagnuTime$DejagnuWallTime
    • -
  • Number of object files compiled: $NumObjects
    • -
  • Number of libraries linked: $NumLibraries
    • -
  • Number of executables linked: $NumExecutables
    • -
  • Build Status: $BuildStatus
    • -
- -

Warnings during the build:

-$WarningsList - -

-
-
Changes from Yesterday -

- -

Changes to CVS:

-
    -
  • Users who committed to CVS: $UserCommitList -
  • Users who updated from CVS: $UserUpdateList -
  • Added Files: $AddedFilesList -
  • Modified Files: $ModifiedFilesList -
  • Removed Files: $RemovedFilesList -

- -

Changes to Warnings:

-

Warnings Added:

-$WarningsAdded -

Warnings Removed:

-$WarningsRemoved - -

Changes in the test suite:

-
    -
  • New Tests: $TestsAdded -
  • Removed Tests: $TestsRemoved -
  • Newly passing tests: $TestsFixed -
  • Newly failing tests: $TestsBroken -
-
- - -

-
-
Dejagnu Test Results -
-
-$DejagnuTestResults -

A complete log of testing Feature and Regression is available for further analysis.

- -

-
-
Changes Over Time -

- - -Here are some charts showing how the LLVM optimizer and code generators are -changing over time. For now we use the Olden benchmark suite to measure this, -but eventually we will switch to using SPEC CPU2000. All programs are run with -"LARGE_PROBLEM_SIZE" enabled. Click on any of the charts to get a larger -version.

- -

Compilation Measurements:

- - - - - -
-
-Size of LLVM bytecode files -		 -
-Time to run the LLVM optimizer on each program -
- -

Program Execution Measurements:

- - - - - - - - - -
-
-Execution time for CBE generated executable -		 -
-Execution time for the LLC generated executable -
-
-Execution time for program in the JIT -
- - - - -

-
-
Program Tests -

- -This section tests LLVM on a variety of programs in the test suite. This -includes benchmark suites like the Olden, McCat, Ptrdist, and SPEC benchmarks as -well as a few random programs with test inputs. This section is meant to track -how stable LLVM is as a whole. A failure in the execution of any test is marked -with an asterisk: `*'. The columns of the tables are:

- -

    -
  1. Program - The name of the program for that row.
    2. -
  2. GCCAS - Time to run LLVM optimizers on the program.
    3. -
  3. Bytecode - The size of the bytecode for the - program
    4. -
  4. Instrs - The number of LLVM instructions in the - compiled bytecode
    5. -
  5. LLC compile - The time taken compile with - LLC (the static backend)
    6. -
  6. JIT codegen - The amount of time spent in the - JIT itself, instead of executing the program.
    7. -
  7. Machine code - The number of bytes of machine - code generated by the JIT.
    8. -
  8. GCC - The time taken to execute the program when compiled - with GCC -O2.
    9. -
  9. CBE - The time taken to execute the program after - compilation through the C backend, compiled with -O2.
    10. -
  10. LLC - How long does the program generated by the static - backend LLC take to execute
    11. -
  11. JIT - The amount of time spent running the - program with the JIT; this includes the code generation phase (listed above) - and actually running the program.
    12. -
  12. GCC/LLC - The speed-up of the LLC output vs the native - GCC output: greater than 1 is a speedup, less than 1 is a slowdown.
    13. -
  13. GCC/CBE - The speed-up of the CBE output vs the native - GCC output: greater than 1 is a speedup, less than 1 is a slowdown.
    14. -
  14. LLC-BETA - How long does the program generated by the static - backend LLC take to execute the program, when compiled with new experimental - features. This is temporary, for tuning.
    15. -

- -A complete log of testing -SingleSource, -MultiSource, and -External programs are -available for further analysis. - -

Programs/External

- -
-
-$ExternalProgramsTable -
- -

Programs/MultiSource

- -
-
-$MultiSourceProgramsTable -
- -

Programs/SingleSource

- -
-
-$SingleSourceProgramsTable -
- - - -- cgit v1.2.3