Bug 218525

Summary: REGRESSION(r268564): Caused 9% binary size increase in WebCore
Product: WebKit Reporter: WebKit Commit Bot <commit-queue>
Component: New BugsAssignee: WebKit Commit Bot <commit-queue>
Status: RESOLVED FIXED    
Severity: Normal CC: annulen, cdumez, darin, esprehn+autocc, ews-watchlist, glenn, gyuyoung.kim, joepeck, kondapallykalyan, macpherson, menard, ryuan.choi, sam, sergio, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 119712, 217623, 218158    
Attachments:
Description Flags
REVERT of r268564 none

WebKit Commit Bot
Reported 2020-11-03 10:43:16 PST
https://trac.webkit.org/changeset/268564 broke the build: Caused 9% binary size increase in WebCore 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
REVERT of r268564 (53.99 KB, patch)
2020-11-03 10:43 PST, WebKit Commit Bot 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
WebKit Commit Bot
Comment 1 2020-11-03 10:43:29 PST
Created attachment 413074 [details] REVERT of r268564 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 revert will be successful. This process takes approximately 15 minutes. If you would like to land the revert faster, you can use the following command: webkit-patch land-attachment ATTACHMENT_ID where ATTACHMENT_ID is the ID of this attachment.
EWS
Comment 2 2020-11-03 10:45:57 PST
Committed r269314: <https://trac.webkit.org/changeset/269314> All reviewed patches have been landed. Closing bug and clearing flags on attachment 413074 [details].
Radar WebKit Bug Importer
Comment 3 2020-11-03 10:46:50 PST
<rdar://problem/71001602>
Note You need to log in before you can comment on or make changes to this bug.