Bug 156741

Summary: REGRESSION(r199712): It caused a serious regression on 32 bit platform (Requested by gskachkov on #webkit).
Product: WebKit Reporter: WebKit Commit Bot <commit-queue>
Component: New BugsAssignee: WebKit Commit Bot <commit-queue>
Status: RESOLVED FIXED    
Severity: Normal CC: ap, gskachkov, keith_miller, mark.lam, msaboff, ossy, saam
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 151113    
Attachments:
Description Flags
ROLLOUT of r199712 none

WebKit Commit Bot
Reported 2016-04-19 06:06:40 PDT
http://trac.webkit.org/changeset/199712 broke the build: It caused a serious regression on 32 bit platform (Requested by gskachkov 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 r199712 (28.85 KB, patch)
2016-04-19 06:07 PDT, WebKit Commit Bot 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
WebKit Commit Bot
Comment 1 2016-04-19 06:07:20 PDT
Created attachment 276718 [details] ROLLOUT of r199712 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.
GSkachkov
Comment 2 2016-04-19 10:54:05 PDT
Comment on attachment 276718 [details] ROLLOUT of r199712 Clearing flags on attachment: 276729 Committed r199712: <http://trac.webkit.org/changeset/199724>
GSkachkov
Comment 3 2016-04-19 10:55:02 PDT
All reviewed patches have been landed. Bug can be closed
Alexey Proskuryakov
Comment 4 2016-04-21 18:19:33 PDT
Why was this bug still in NEW state?
Alexey Proskuryakov
Comment 5 2016-04-21 18:20:11 PDT
*** Bug 156740 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.