framework/summary.py: Replace Section heading with docstrings

The sections headings are not really that useful, but they might as well
be kept as class level docstrings instead of being thrown away.

V2: Correct spelling error

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
piglit-summary-html.py: Fix listfile syntax

This patch changes the listfile syntax to be newline separated. Further
it actually hooks up the plumbing allowing the -l/--list option to
actually work

V3: Adds this patch

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
framework/summary.py: Adds new summary class and two support classes

This new summary class (currently NewSummary), is a complete redesign of
the summary generation system. Much of the code in summary was not
commented, and also not clear as to what it was doing, making it very
difficult to maintain and even more difficult to improve. The other
problem with the code was architecturally it was clobbered together,
doing some of the work in the summary.py file, and some of the work in
the piglit-summary-html.py file.

The new summary class does all of it's work in the summary.py file, and
from an API point of view, in one class. The summary class uses it's
constructor to build lists of passes, failures, skips, problems, etc.
and then uses methods to generate output. The reference implementation
of that kind of method is for generating HTML, but in theory it could be
used to generate anything: XML, csv lists, printed lists ala
piglit-summary, etc.

Also updates the .gitignore file to ignore some generated content
created by this class.

V3: - Corrects some spelling mistakes and some comments that had old
	  method/variable names
	- renames several methods/functions
    - moves sanitizePath to a toplevel function
	- changes sanitizePath to use lambda per ken
    - Moves buildDictionary to a helper function instead of private
	  method
templates: adds mako templates for new summary code

Adds the actual templates used to by the new mako based summary code.

V3: Replace tabs with spaces like python code
    Rename test_index.mako to testrun_info.mako
    Refactor testrun_info.mako links bar generation

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
piglit-summary-py: Use the new summary class to generate HTML

Drops almost all of the code used in this file, all of that
functionality is now handled in the summary class. Instead, the majority
of this file is just the argparse instance, and a few short lines
calling the new summary class.

V2: Fixes the -l/--list syntax
V3: Changes the listfile syntax to match the newline seperated format

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
templates: Remove old HTML templates

These template files are no longer used, and so they should be removed

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
templates/index.css: make some css more exclusive

Change the div:nth-child for operating on everything except head to only
working on group. This is lays groundwork for some other changes.

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
summary: Build subdirectories for subtest result pages

With 10,000+ tests all living in the same folder it can be hard to
identify a single file, especially when trying to work with the HTML
generation itself. This patch changes the behavior so that each test
has a directory tree for the group results with tests under it (ie
spec/GLSL 1.0/foo/bar/test.html)

A side effect of this is that the group names of tests don't have to be
altered to create a valid name (since the slashes in the group names
just become the slashes in the folder structure) and this was the single
most expensive operation of HTML generation (about 1/3 of the total
time). This is a tidy little speedup.

V3: Correct some spelling errors/remove excess comments

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
test_result.mako: Drop redundant status and result field

In the old summary code one was set equal to the other, and then
written. In order to produce the same output they were both brought over
to the mako code. But they're rather silly and worthless and only one
should be kept.

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
HTML summary: Provides means to exclude generating test result files

This provides a switch and method for excluding the generation of the
test result HTML files (those that live under <testrun name>/). This
allows the user to trade some verbosity in the results for a significant
increase in generation speed. A run of quick.tests with all options
enabled takes ~5.5 seconds, with just pass and skip disabled it only
takes ~2.5 seconds. This only becomes more significant as more testsruns
are added the HTML page.

V3: Remove some bad comments

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
summary.py: Change skip to 'Not Run' for tests not run

When comparing two test results the current behavior sets a status of
skip for tests that were not run in one set of results. This is
confusing and silly, so instead give them a status of N/A which gives a
clear understanding of what skipped, and what simply didn't run either
by exclusion or because it didn't exist yet.

V3: Change N/A to "Not Run"
V4: Fixes "Not Run" to not be compared for fixes regressions, problem,
    and changes

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>