RESOLVED FIXED Bug 63716
TestFailures page should try to infer which commit caused a failure by looking at commit logs 
https://bugs.webkit.org/show_bug.cgi?id=63716
Summary TestFailures page should try to infer which commit caused a failure by lookin...
Adam Roben (:aroben)
Reported 2011-06-30 07:19:08 PDT
In cases where a test started failing but the regression range is non-empty (i.e., there are multiple possibly-guilty revisions), it would be nice for TestFailures to look at the commit logs for the possibly-guilty revisions and see if any of them modified the affected test. Then it could call out those revisions as particularly suspicious.
Attachments
Identify revisions that modified failing tests on TestFailures page (11.32 KB, patch)
2011-06-30 12:35 PDT, Adam Roben (:aroben) 		ddkilzer: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Adam Roben (:aroben)
Comment 1 2011-06-30 09:22:00 PDT
We can get commit logs from Trac, but we'll need to add some CORS headers to trac.webkit.org to allow XHRs from build.webkit.org to succeed.
Adam Roben (:aroben)
Comment 2 2011-06-30 12:35:13 PDT
Created attachment 99355 [details] Identify revisions that modified failing tests on TestFailures page
Adam Roben (:aroben)
Comment 3 2011-06-30 12:35:38 PDT
Comment on attachment 99355 [details] Identify revisions that modified failing tests on TestFailures page Note that this patch won't actually work until we add CORS headers to trac.webkit.org to allow XHRs from build.webkit.org to work.
David Kilzer (:ddkilzer)
Comment 4 2011-06-30 13:01:39 PDT
Comment on attachment 99355 [details] Identify revisions that modified failing tests on TestFailures page r=me
Adam Roben (:aroben)
Comment 5 2011-06-30 13:03:53 PDT
Committed r90153: <http://trac.webkit.org/changeset/90153>
Note You need to log in before you can comment on or make changes to this bug.