Bug 63203

Summary: REGRESSION(r89489): Broke chromium mac build on build.webkit.org (Requested by abarth 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: fishd
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 62999    
Attachments:
Description Flags
ROLLOUT of r89489 none

WebKit Review Bot
Reported 2011-06-22 16:35:41 PDT
http://trac.webkit.org/changeset/89489 broke the build: Broke chromium mac build on build.webkit.org (Requested by abarth 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 r89489 (31.33 KB, patch)
2011-06-22 16:36 PDT, WebKit Review Bot 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
WebKit Review Bot
Comment 1 2011-06-22 16:36:04 PDT
Created attachment 98263 [details] ROLLOUT of r89489 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 Review Bot
Comment 2 2011-06-22 16:56:06 PDT
Comment on attachment 98263 [details] ROLLOUT of r89489 Clearing flags on attachment: 98263 Committed r89496: <http://trac.webkit.org/changeset/89496>
WebKit Review Bot
Comment 3 2011-06-22 16:56:10 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.