RESOLVED FIXED Bug 88758
REGRESSION(r119955): Breaks Chromium compile - Chromium depends on removed API (Requested by dominicc on #webkit).
https://bugs.webkit.org/show_bug.cgi?id=88758
Summary REGRESSION(r119955): Breaks Chromium compile - Chromium depends on removed AP...
WebKit Review Bot
Reported 2012-06-10 23:52:30 PDT
http://trac.webkit.org/changeset/119955 broke the build: Breaks Chromium compile - Chromium depends on removed API (Requested by dominicc 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 r119955 (23.47 KB, patch)
2012-06-10 23:53 PDT, WebKit Review Bot
no flags
WebKit Review Bot
Comment 1 2012-06-10 23:53:14 PDT
Created attachment 146793 [details] ROLLOUT of r119955 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.
mitz
Comment 2 2012-06-10 23:58:53 PDT
(In reply to comment #0) > http://trac.webkit.org/changeset/119955 broke the build: > Breaks Chromium compile - Chromium depends on removed API (Requested by dominicc on #webkit). Can anyone explain how Chromium depends on OS X WebKit private API?
WebKit Review Bot
Comment 3 2012-06-10 23:58:55 PDT
Comment on attachment 146793 [details] ROLLOUT of r119955 Clearing flags on attachment: 146793 Committed r119957: <http://trac.webkit.org/changeset/119957>
WebKit Review Bot
Comment 4 2012-06-10 23:58:59 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.