Bug 126332

Summary: REGRESSION(r161157): Broke WebKit2 on Mountain Lion (Requested by ap on #webkit).
Product: WebKit Reporter: WebKit Commit Bot <commit-queue>
Component: New BugsAssignee: WebKit Commit Bot <commit-queue>
Status: RESOLVED FIXED    
Severity: Normal CC: andersca, kling
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 126308    
Attachments:
Description Flags
ROLLOUT of r161157 none

WebKit Commit Bot
Reported 2013-12-30 22:47:21 PST
http://trac.webkit.org/changeset/161157 broke the build: Broke WebKit2 on Mountain Lion (Requested by ap on #webkit). This is an automatic bug report generated by webkitbot. 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 fail.
Attachments
ROLLOUT of r161157 (29.32 KB, patch)
2013-12-30 22:47 PST, WebKit Commit Bot
no flags
WebKit Commit Bot
Comment 1 2013-12-30 22:47:42 PST
Created attachment 220149 [details] ROLLOUT of r161157 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.
Alexey Proskuryakov
Comment 2 2013-12-30 22:48:54 PST
Comment on attachment 220149 [details] ROLLOUT of r161157 WebKit2 on Mountain Lion is still broken after all follow-up fixes.
WebKit Commit Bot
Comment 3 2013-12-30 22:50:38 PST
Comment on attachment 220149 [details] ROLLOUT of r161157 Clearing flags on attachment: 220149 Committed r161173: <http://trac.webkit.org/changeset/161173>
WebKit Commit Bot
Comment 4 2013-12-30 22:50:39 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.