Bug 134157

Summary: REGRESSION(r170244): GTK/EFL bindings generator works differently, making this patch not work there. Will fix entire patch after a rollout. (Requested by bradee-oh on #webkit).
Product: WebKit Reporter: WebKit Commit Bot <commit-queue>
Component: New BugsAssignee: WebKit Commit Bot <commit-queue>
Status: RESOLVED FIXED    
Severity: Normal CC: beidson, timothy
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 134108    
Attachments:
Description Flags
ROLLOUT of r170244 none

WebKit Commit Bot
Reported 2014-06-21 09:20:54 PDT
http://trac.webkit.org/changeset/170244 broke the build: GTK/EFL bindings generator works differently, making this patch not work there. Will fix entire patch after a rollout. (Requested by bradee-oh 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 r170244 (69.45 KB, patch)
2014-06-21 09:21 PDT, WebKit Commit Bot
no flags
WebKit Commit Bot
Comment 1 2014-06-21 09:21:27 PDT
Created attachment 233536 [details] ROLLOUT of r170244 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 2014-06-21 09:25:10 PDT
Comment on attachment 233536 [details] ROLLOUT of r170244 Clearing flags on attachment: 233536 Committed r170246: <http://trac.webkit.org/changeset/170246>
WebKit Commit Bot
Comment 3 2014-06-21 09:25:12 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.