Bug 143250

Summary: REGRESSION(r182172): Since this class is an API object, we don't know for sure when it will be destroyed. (Requested by kling on #webkit).
Product: WebKit Reporter: WebKit Commit Bot <commit-queue>
Component: New BugsAssignee: WebKit Commit Bot <commit-queue>
Status: RESOLVED FIXED    
Severity: Normal CC: kling, thorton
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 143231    
Attachments:
Description Flags
ROLLOUT of r182172 none

WebKit Commit Bot
Reported 2015-03-30 20:24:16 PDT
http://trac.webkit.org/changeset/182172 broke the build: Since this class is an API object, we don't know for sure when it will be destroyed. (Requested by kling 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 r182172 (1.59 KB, patch)
2015-03-30 20:24 PDT, WebKit Commit Bot 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
WebKit Commit Bot
Comment 1 2015-03-30 20:24:42 PDT
Created attachment 249792 [details] ROLLOUT of r182172 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 Commit Bot
Comment 2 2015-03-30 20:27:48 PDT
Comment on attachment 249792 [details] ROLLOUT of r182172 Clearing flags on attachment: 249792 Committed r182173: <http://trac.webkit.org/changeset/182173>
WebKit Commit Bot
Comment 3 2015-03-30 20:27:51 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.