Bug 49784

Summary: REGRESSION(r72357): It broke test-webkitpy tests since the patch didn't have the corresponding test update (Requested by kinuko 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: commit-queue, kinuko, ojan
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Other   
OS: OS X 10.5   
Bug Depends on:    
Bug Blocks: 49702    
Attachments:
Description Flags
ROLLOUT of r72357 none

WebKit Review Bot
Reported 2010-11-18 20:43:23 PST
http://trac.webkit.org/changeset/72357 broke the build: It broke test-webkitpy tests since the patch didn't have the corresponding test update (Requested by kinuko 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 r72357 (3.41 KB, patch)
2010-11-18 20:43 PST, WebKit Review Bot
no flags
WebKit Review Bot
Comment 1 2010-11-18 20:43:45 PST
Created attachment 74350 [details] ROLLOUT of r72357 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.
Kinuko Yasuda
Comment 2 2010-11-18 21:16:33 PST
Comment on attachment 74350 [details] ROLLOUT of r72357 Clearing flags on attachment: 74350 Committed r72365: <http://trac.webkit.org/changeset/72365>
Kinuko Yasuda
Comment 3 2010-11-18 21:16:38 PST
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.