RESOLVED FIXED 44660
REGRESSION(r66074): Chromium canary turned red (Requested by yuzo on #webkit). 
https://bugs.webkit.org/show_bug.cgi?id=44660
Summary REGRESSION(r66074): Chromium canary turned red (Requested by yuzo on #webkit).
WebKit Review Bot
Reported 2010-08-25 20:52:43 PDT
http://trac.webkit.org/changeset/66074 broke the build: Chromium canary turned red (Requested by yuzo 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 r66074 (13.89 KB, patch)
2010-08-25 20:52 PDT, WebKit Review Bot 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
WebKit Review Bot
Comment 1 2010-08-25 20:52:58 PDT
Created attachment 65522 [details] ROLLOUT of r66074 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 --ignore-builders where ATTACHMENT_ID is the ID of this attachment.
WebKit Commit Bot
Comment 2 2010-08-25 21:02:41 PDT
Comment on attachment 65522 [details] ROLLOUT of r66074 Clearing flags on attachment: 65522 Committed r66079: <http://trac.webkit.org/changeset/66079>
WebKit Commit Bot
Comment 3 2010-08-25 21:02:46 PDT
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.