Bug 63281 - TestFailures page fetches build JSON for every build, which is slow and limits history to the last build master restart
Summary: TestFailures page fetches build JSON for every build, which is slow and limit...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL: http://build.webkit.org/TestFailures/
Keywords:
Depends on: 63280
Blocks:
  Show dependency treegraph
 
Reported: 2011-06-23 13:22 PDT by Adam Roben (:aroben)
Modified: 2011-06-23 14:47 PDT (History)
1 user (show)

See Also:


Attachments
Avoid fetching JSON data when possible on TestFailures page to determine if old-run-webkit-tests exited early (5.79 KB, patch)
2011-06-23 14:29 PDT, Adam Roben (:aroben)
ddkilzer: review+
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Roben (:aroben) 2011-06-23 13:22:31 PDT
TestFailures page fetches build JSON for every build, in addition to the results.html page. It does this so it can determine whether run-webkit-tests exited early due to too many failures/crashes/timeouts. But this is slow, and limits history to whenever the build master was last restarted.

It would be much better if we could just pull this information out of results.html. Then we'd only have to do one request per build, and history would be practically unlimited.
Comment 1 Adam Roben (:aroben) 2011-06-23 13:28:45 PDT
After bug 63280 is fixed, we can change TestFailures to only look at the build JSON if we're dealing with a build older than whatever revision bug 63280 was fixed in.
Comment 2 Adam Roben (:aroben) 2011-06-23 14:29:30 PDT
Created attachment 98404 [details]
Avoid fetching JSON data when possible on TestFailures page to determine if old-run-webkit-tests exited early
Comment 3 David Kilzer (:ddkilzer) 2011-06-23 14:36:51 PDT
Comment on attachment 98404 [details]
Avoid fetching JSON data when possible on TestFailures page to determine if old-run-webkit-tests exited early

View in context: https://bugs.webkit.org/attachment.cgi?id=98404&action=review

r=me

> Tools/BuildSlaveSupport/build.webkit.org-config/public_html/TestFailures/Buildbot.js:75
> +    resultsHTMLForBuildIncludesTooManyFailuresInfo: function(buildName) {

See next comment.

> Tools/BuildSlaveSupport/build.webkit.org-config/public_html/TestFailures/Builder.js:247
> +        var resultsHTMLIncludesTooManyFailuresInfo = this.buildbot.resultsHTMLForBuildIncludesTooManyFailuresInfo(buildName);

I don't like "Includes" in this variable name because that implies (just reading the variable name) that this particular build has info about too many failures.  How about using "Supports" instead of "Includes"?

var resultsHTMLSupportsTooManyFailuresInfo = this.buildbot.resultsHTMLForBuildSupportsTooManyFailuresInfo(buildName);
Comment 4 Adam Roben (:aroben) 2011-06-23 14:38:22 PDT
Comment on attachment 98404 [details]
Avoid fetching JSON data when possible on TestFailures page to determine if old-run-webkit-tests exited early

View in context: https://bugs.webkit.org/attachment.cgi?id=98404&action=review

>> Tools/BuildSlaveSupport/build.webkit.org-config/public_html/TestFailures/Builder.js:247
>> +        var resultsHTMLIncludesTooManyFailuresInfo = this.buildbot.resultsHTMLForBuildIncludesTooManyFailuresInfo(buildName);
> 
> I don't like "Includes" in this variable name because that implies (just reading the variable name) that this particular build has info about too many failures.  How about using "Supports" instead of "Includes"?
> 
> var resultsHTMLSupportsTooManyFailuresInfo = this.buildbot.resultsHTMLForBuildSupportsTooManyFailuresInfo(buildName);

Good suggestion. I'll go with that!
Comment 5 Adam Roben (:aroben) 2011-06-23 14:47:35 PDT
Committed r89619: <http://trac.webkit.org/changeset/89619>