Bug 43285

Summary: REGRESSION(r64375): Rolling back because it broke the chromium canary bots, possibly due to expectations that weren't moved (Requested by atwilson on #webkit).
Product: WebKit Reporter: WebKit Review Bot <webkit.review.bot>
Component: New BugsAssignee: WebKit Review Bot <webkit.review.bot>
Status: RESOLVED INVALID    
Severity: Normal CC: atwilson, levin
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Other   
OS: OS X 10.5   
Bug Depends on:    
Bug Blocks: 43261    
Attachments:
Description Flags
ROLLOUT of r64375 none

WebKit Review Bot
Reported 2010-07-30 16:28:07 PDT
http://trac.webkit.org/changeset/64375 broke the build: Rolling back because it broke the chromium canary bots, possibly due to expectations that weren't moved (Requested by atwilson 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 r64375 (8.29 KB, patch)
2010-07-30 16:28 PDT, WebKit Review Bot 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
WebKit Review Bot
Comment 1 2010-07-30 16:28:24 PDT
Created attachment 63120 [details] ROLLOUT of r64375 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.
Andrew Wilson
Comment 2 2010-07-30 16:53:53 PDT
Landed this change manually using git revert instead, referencing the original bug.
Note You need to log in before you can comment on or make changes to this bug.