Bug 142910 - REGRESSION(r181782): Broke the 32-bit builds (Requested by jessieberlin on #webkit).
Summary: REGRESSION(r181782): Broke the 32-bit builds (Requested by jessieberlin on #w...
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: WebKit Commit Bot
URL:
Keywords:
Depends on:
Blocks: 142893
  Show dependency tree / graph
 
Reported: 2015-03-20 08:06 PDT by WebKit Commit Bot
Modified: 2015-03-20 12:32 PDT (History)
3 users (show)

See Also:

Attachments
ROLLOUT of r181782 (11.21 KB, patch)
2015-03-20 08:06 PDT, WebKit Commit Bot 		no flags Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description WebKit Commit Bot 2015-03-20 08:06:09 PDT 
http://trac.webkit.org/changeset/181782 broke the build:
Broke the 32-bit builds (Requested by jessieberlin 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.
Comment 1 WebKit Commit Bot 2015-03-20 08:06:44 PDT 
Created attachment 249115 [details]
ROLLOUT of r181782

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 Chris Dumez 2015-03-20 08:30:32 PDT 
I think the bots having this issue just need a clean build. Somehow some of them failed to rebuild WKPage.cpp when doing the incremental build.
Comment 3 Chris Dumez 2015-03-20 12:32:19 PDT 
False alarm, a clean build fixed the problem.