RESOLVED FIXED 72109
REGRESSION(r99826): "Likely causing test flakiness" (Requested by tonyg-cr on #webkit). 
https://bugs.webkit.org/show_bug.cgi?id=72109
Summary REGRESSION(r99826): "Likely causing test flakiness" (Requested by tonyg-cr on...
WebKit Review Bot
Reported 2011-11-11 03:27:01 PST
http://trac.webkit.org/changeset/99826 broke the build: "Likely causing test flakiness" (Requested by tonyg-cr on #webkit). This is an automatic bug report generated by the sheriff-bot. If this bug report was created because of a flaky test, please file a bug for the flaky test (if we don't already have one on file) and dup this bug against that bug so that we can track how often these flaky tests case pain. "Only you can prevent forest fires." -- Smokey the Bear
Attachments
ROLLOUT of r99826 (13.46 KB, patch)
2011-11-11 03:27 PST, WebKit Review Bot 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
WebKit Review Bot
Comment 1 2011-11-11 03:27:29 PST
Created attachment 114660 [details] ROLLOUT of r99826 Any committer can land this patch automatically by marking it commit-queue+. The commit-queue will build and test the patch before landing to ensure that the rollout will be successful. This process takes approximately 15 minutes. If you would like to land the rollout faster, you can use the following command: webkit-patch land-attachment ATTACHMENT_ID where ATTACHMENT_ID is the ID of this attachment.
Tony Gentilcore
Comment 2 2011-11-11 03:30:34 PST
I suspect this patch is causing bug 72039 and I can't reproduce that flakiness locally. So I'm provisionally rolling this out to verify/falsify my theory. I will keep a very close eye on this and reland immediately if I'm wrong about this patch.
Tony Gentilcore
Comment 3 2011-11-11 03:47:24 PST
Comment on attachment 114660 [details] ROLLOUT of r99826 Clearing flags on attachment: 114660 Committed r99940: <http://trac.webkit.org/changeset/99940>
Tony Gentilcore
Comment 4 2011-11-11 03:47:31 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.