[Bug 48215] New: Add size, time and test unit failures tabs to the JobDetails page

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48215

Bug ID: 48215
           Summary: Add size, time and test unit failures tabs to the
                    JobDetails page
           Product: Wine-Testbot
           Version: unspecified
          Hardware: x86
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Currently the JobDetails page only provides access to each task's reports and
logs. This can make it hard to figure out which test units have failures (bug
47904) and harder still to compare the test unit failures across the tasks.

This is ok when testing regular patches since each task typically only runs a
single test unit (except for Wine tasks). But for WineTest tasks it would be
useful to be able to compare which test units failed for each task. The current
workaround is to use test.winehq.org for that, but there too comparing results
as its limitations (see bug 15477), and sometimes the reports a rejected which
is when it would be nice to be able to dig into them.

Similarly it would be quite nice to be able to have a table showing the run
time an report size across test unit and tasks.

One way to present this would be to have a list of tabs at the top of the
JobDetails page:

Reports  |  Unit Failures  |  Size  |  Run time

The Reports tab would show the usual task reports while the other tabs would
show tables with one column per task, one line per test unit and the specified
information in the cells. Ideally clicking on a column header would sort the
table on that column.

This is reasonably easy to do at the JobDetails level: when parsing the reports
we can extract all the required information. All that would be required is to
save it to a summary file (one line per test unit with the count of failures,
size, run time). That would make it easy and quick for JobDetails to retrieve
the information and then it's a matter of getting the HTML side in place.