[LLVMbugs] [Bug 357] NEW: Improvements For Nightly Tester

bugzilla-daemon at cs.uiuc.edu bugzilla-daemon at cs.uiuc.edu
Thu Jun 3 16:48:23 PDT 2004


           Summary: Improvements For Nightly Tester
           Product: Test Suite
           Version: trunk
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Nightly Tester
        AssignedTo: rspencer at x10sys.com
        ReportedBy: rspencer at x10sys.com
                CC: sabre at nondot.org

This is just a place to put all my reminders for some improvements to the 
nightly tester. The import of this isn't high enough to warrant separate bugs 
for each feature so I'm collecting them here.  Here's the list:

1. Make line plots use color as well as line style for better readability.
2. Use a more compressed date format (MM/DD/YY) to make X-axis labels readable
3. Reformat the compilation log into a table of "CPU" and "Elapsed" times.
4. For added and modified files, print out number of lines added/removed.
5. Under Compilation Measurements, add plots for bytecode read/write times.
6. Under Program Execution Measurements, cap the Y axis at some value like
   10xmean and label spikes with actual value. This allows the plot to have 
   more resolution (take a look at CBE execution time. You can't see the forest
   for the trees).
7. In the timing tables, use a smaller font for the data so the whole table can
   be within a normal page width (max 1024 pixels). Break tables up if needed.
8. Fix title of rightmost 3 columns in tables so the title doesn't dictate the
   width of the column.
9. In Feature & Regression tests, omit XFAIL output.
10. In Feature & Regression tests, put STATISTICS first, then TEST RESULTS.
11. Compare CBE execution times for optimized and non-optimized executions so
    we can track how much optimizer is improving execution time.

Good. Now I don't have to remember all that any more!

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

More information about the llvm-bugs mailing list