Bug 490554 - Restore "summary table" on a build's DL page
Summary: Restore "summary table" on a build's DL page
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 4.6   Edit
Hardware: PC Linux
: P3 major (vote)
Target Milestone: 4.6 M7   Edit
Assignee: David Williams CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 487044 490232 490440
Blocks: 461797
  Show dependency tree
 
Reported: 2016-03-28 21:20 EDT by David Williams CLA
Modified: 2016-03-31 06:24 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2016-03-28 21:20:07 EDT 
+++ This bug was initially created as a clone of Bug #490440 +++

Fixing Bug 490440 requires some fairly large conceptual changes in the build scripts. This has a way of exposing previously unknown bugs. One of those is that the summary table on DL page for a build was blank. To get those, we "call back" to Hudson with the build name and number and are returned a small XML file with the data. 

My guess is it is now "look up" that file name with the "full key", instead of the simply job name. 

In any case, I commented out that Summary section, since to have nothing there, is better than having a blank table. 

Once the JUnit detailed summary table is working correctly, I will look at restoring the summary.
Comment 1 David Williams CLA 2016-03-30 15:20:34 EDT 
http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?id=ab4168b14d12c0f33a122873c3db4e683b9e318d

Should be fixed in tonight's "nightly" (3/30/2016). 

The code that "computed" the values before, from the XML files, was overly complex, and adding the "jobname" to the "testConfiguration" values actually allowed this part of the code to be simplified quite a bit. (Whereas my first hack at it just added to the complexity).