Bug 74069

Summary: REGRESSION(r102323): Caused Chromium and GTK build failure (Requested by bashi 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: fsamuel, simon.fraser
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 64512    
Attachments:
Description Flags
ROLLOUT of r102323 none

WebKit Review Bot
Reported 2011-12-08 02:04:45 PST
http://trac.webkit.org/changeset/102323 broke the build: Caused Chromium and GTK build failure (Requested by bashi 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 r102323 (32.76 KB, patch)
2011-12-08 02:05 PST, WebKit Review Bot
no flags
WebKit Review Bot
Comment 1 2011-12-08 02:05:17 PST
Created attachment 118351 [details] ROLLOUT of r102323 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.
WebKit Review Bot
Comment 2 2011-12-08 02:12:38 PST
Comment on attachment 118351 [details] ROLLOUT of r102323 Clearing flags on attachment: 118351 Committed r102324: <http://trac.webkit.org/changeset/102324>
WebKit Review Bot
Comment 3 2011-12-08 02:12:42 PST
All reviewed patches have been landed. Closing bug.
Fady Samuel
Comment 4 2011-12-08 06:26:01 PST
Why was this reverted? All the EWS bots were green, I don't see how this patch could have caused build failures!
Note You need to log in before you can comment on or make changes to this bug.