RESOLVED FIXED Bug 54318
REGRESSION(r78044): Broke Safari extensions (Requested by eseidel on #webkit).
https://bugs.webkit.org/show_bug.cgi?id=54318
Summary REGRESSION(r78044): Broke Safari extensions (Requested by eseidel on #webkit).
WebKit Review Bot
Reported 2011-02-11 15:28:13 PST
http://trac.webkit.org/changeset/78044 broke the build: Broke Safari extensions (Requested by eseidel 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 r78044 (13.90 KB, patch)
2011-02-11 15:28 PST, WebKit Review Bot
no flags
WebKit Review Bot
Comment 1 2011-02-11 15:28:35 PST
Created attachment 82193 [details] ROLLOUT of r78044 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.
Eric Seidel (no email)
Comment 2 2011-02-11 15:29:06 PST
I have a fix in progress, but no need to block Apple from shipping, etc.
WebKit Commit Bot
Comment 3 2011-02-11 17:17:17 PST
Comment on attachment 82193 [details] ROLLOUT of r78044 Clearing flags on attachment: 82193 Committed r78395: <http://trac.webkit.org/changeset/78395>
WebKit Commit Bot
Comment 4 2011-02-11 17:17:22 PST
All reviewed patches have been landed. Closing bug.
WebKit Review Bot
Comment 5 2011-02-13 02:19:37 PST
http://trac.webkit.org/changeset/78395 might have broken SnowLeopard Intel Release (WebKit2 Tests) The following tests are not passing: fast/loader/empty-embed-src-attribute.html
Note You need to log in before you can comment on or make changes to this bug.