RESOLVED FIXED 69170
REGRESSION(r96422): Broke Windows build and kling wanted to roll it out as well (Requested by rniwa on #webkit). 
https://bugs.webkit.org/show_bug.cgi?id=69170
Summary REGRESSION(r96422): Broke Windows build and kling wanted to roll it out as we...
WebKit Review Bot
Reported 2011-09-30 14:16:44 PDT
http://trac.webkit.org/changeset/96422 broke the build: Broke Windows build and kling wanted to roll it out as well (Requested by rniwa 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 r96422 (3.57 KB, patch)
2011-09-30 14:17 PDT, WebKit Review Bot 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
WebKit Review Bot
Comment 1 2011-09-30 14:17:19 PDT
Created attachment 109345 [details] ROLLOUT of r96422 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.
WebKit Review Bot
Comment 2 2011-09-30 14:22:50 PDT
Comment on attachment 109345 [details] ROLLOUT of r96422 Clearing flags on attachment: 109345 Committed r96425: <http://trac.webkit.org/changeset/96425>
WebKit Review Bot
Comment 3 2011-09-30 14:22:54 PDT
All reviewed patches have been landed. Closing bug.
Ryosuke Niwa
Comment 4 2011-09-30 14:40:59 PDT
Reopen the bug since the patch was rolled out in http://trac.webkit.org/changeset/96425.
Andreas Kling
Comment 5 2011-10-05 04:41:00 PDT
Relanded in <http://trac.webkit.org/changeset/96693>.
Note You need to log in before you can comment on or make changes to this bug.