Bug 230854

Summary: REGRESSION(r283102): It regresses JetStream2 on iOS devices
Product: WebKit Reporter: WebKit Commit Bot <commit-queue>
Component: New BugsAssignee: WebKit Commit Bot <commit-queue>
Status: RESOLVED FIXED    
Severity: Normal CC: ayumi_kojima, saam, webkit-bug-importer, ysuzuki
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 229223    
Attachments:
Description Flags
REVERT of r283102 none

WebKit Commit Bot
Reported 2021-09-27 12:30:24 PDT
https://commits.webkit.org/r283102 introduced a regression: It regresses JetStream2 on iOS devices 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 r283102 (632.64 KB, patch)
2021-09-27 12:31 PDT, WebKit Commit Bot 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
WebKit Commit Bot
Comment 1 2021-09-27 12:31:00 PDT
Created attachment 439378 [details] REVERT of r283102 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 2021-09-27 12:33:27 PDT
Committed r283129 (242187@main): <https://commits.webkit.org/242187@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 439378 [details].
Radar WebKit Bug Importer
Comment 3 2021-09-27 12:34:19 PDT
<rdar://problem/83586032>
Alexey Proskuryakov
Comment 4 2021-09-27 12:50:31 PDT
*** Bug 230847 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.