Bug 165853

Summary: REGRESSION(r209795): rolled out the wrong revision (Requested by pizlo on #webkit).
Product: WebKit Reporter: WebKit Commit Bot <commit-queue>
Component: New BugsAssignee: WebKit Commit Bot <commit-queue>
Status: RESOLVED FIXED    
Severity: Normal CC: barraclough
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 165741    
Attachments:
Description Flags
ROLLOUT of r209795 none

WebKit Commit Bot
Reported 2016-12-14 09:21:24 PST
http://trac.webkit.org/changeset/209795 broke the build: rolled out the wrong revision (Requested by pizlo on #webkit). This is an automatic bug report generated by webkitbot. 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 fail.
Attachments
ROLLOUT of r209795 (53.98 KB, patch)
2016-12-14 09:21 PST, WebKit Commit Bot
no flags
WebKit Commit Bot
Comment 1 2016-12-14 09:21:44 PST
Created attachment 297094 [details] ROLLOUT of r209795 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.
Filip Pizlo
Comment 2 2016-12-14 09:22:41 PST
Comment on attachment 297094 [details] ROLLOUT of r209795 I just landed the proper fix for the memory regression in https://trac.webkit.org/changeset/209807
WebKit Commit Bot
Comment 3 2016-12-14 09:25:54 PST
Comment on attachment 297094 [details] ROLLOUT of r209795 Clearing flags on attachment: 297094 Committed r209808: <http://trac.webkit.org/changeset/209808>
WebKit Commit Bot
Comment 4 2016-12-14 09:25:57 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.