Bug 47547

Summary: REGRESSION(r69589): Wrong patch landed from a bug with two patches (Requested by mrobinson 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: mrobinson
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Other   
OS: OS X 10.5   
Bug Depends on:    
Bug Blocks: 44261    
Attachments:
Description Flags
ROLLOUT of r69589 none

WebKit Review Bot
Reported 2010-10-12 11:32:44 PDT
http://trac.webkit.org/changeset/69589 broke the build: Wrong patch landed from a bug with two patches (Requested by mrobinson 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 r69589 (39.75 KB, patch)
2010-10-12 11:33 PDT, WebKit Review Bot 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
WebKit Review Bot
Comment 1 2010-10-12 11:33:05 PDT
Created attachment 70546 [details] ROLLOUT of r69589 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.
Martin Robinson
Comment 2 2010-10-12 14:44:50 PDT
Comment on attachment 70546 [details] ROLLOUT of r69589 Clearing flags on attachment: 70546 Committed r69606: <http://trac.webkit.org/changeset/69606>
Martin Robinson
Comment 3 2010-10-12 14:44:59 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.