Bug 117924

Summary: REGRESSION(r151021): caused regressions on Qt and GTK (#117141 and #117688) (Requested by philn on #webkit).
Product: WebKit Reporter: WebKit Commit Bot <commit-queue>
Component: New BugsAssignee: WebKit Commit Bot <commit-queue>
Severity: Normal CC: pnormand, slomo
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 115352    
Description Flags
ROLLOUT of r151021 none

Description WebKit Commit Bot 2013-06-24 02:29:04 PDT
http://trac.webkit.org/changeset/151021 broke the build:
caused regressions on Qt and GTK (#117141 and #117688) (Requested by philn 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
Comment 1 WebKit Commit Bot 2013-06-24 02:29:31 PDT
Created attachment 205279 [details]
ROLLOUT of r151021

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.
Comment 2 WebKit Commit Bot 2013-06-24 02:33:21 PDT
Comment on attachment 205279 [details]
ROLLOUT of r151021

Clearing flags on attachment: 205279

Committed r151903: <http://trac.webkit.org/changeset/151903>
Comment 3 WebKit Commit Bot 2013-06-24 02:33:23 PDT
All reviewed patches have been landed.  Closing bug.
Comment 4 Sebastian Dröge (slomo) 2013-06-27 05:55:31 PDT
Shouldn't we keep this bug open until the original patch is fixed to not cause regressions? Because the original patch was actually fixing a quite serious bug...
Comment 5 Philippe Normand 2013-06-27 06:01:17 PDT
Bug 115352 was reopened, the patch can be updated there.