Bug 89021

Summary: REGRESSION(r120220): The patch broke build Chromium Win Release (Requested by wangxianzhu on #webkit).
Product: WebKit Reporter: WebKit Review Bot <webkit.review.bot>
Component: New BugsAssignee: WebKit Review Bot <webkit.review.bot>
Status: RESOLVED FIXED    
Severity: Normal CC: abarth, wangxianzhu
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 88802    
Attachments:
Description Flags
ROLLOUT of r120220 none

WebKit Review Bot
Reported 2012-06-13 10:52:15 PDT
http://trac.webkit.org/changeset/120220 broke the build: The patch broke build Chromium Win Release (Requested by wangxianzhu 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 r120220 (14.58 KB, patch)
2012-06-13 10:53 PDT, WebKit Review Bot 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
WebKit Review Bot
Comment 1 2012-06-13 10:53:27 PDT
Created attachment 147361 [details] ROLLOUT of r120220 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.
Xianzhu Wang
Comment 2 2012-06-13 11:04:25 PDT
Comment on attachment 147361 [details] ROLLOUT of r120220 Clearing flags on attachment: 147361 Committed r120226: <http://trac.webkit.org/changeset/120226>
Xianzhu Wang
Comment 3 2012-06-13 11:04:43 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.