Bug 244740

Summary: [ iOS macOS ] http/wpt/cross-origin-opener-policy/non-secure-to-secure-context-navigation.https.html is a flaky failure
Product: WebKit Reporter: Hercules Hjalmarsson <hhjalmarsson>
Component: New BugsAssignee: Chris Dumez <cdumez>
Status: RESOLVED FIXED    
Severity: Normal CC: cdumez, webkit-bot-watchers-bugzilla, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   

Hercules Hjalmarsson
Reported 2022-09-02 16:40:45 PDT
http/wpt/cross-origin-opener-policy/non-secure-to-secure-context-navigation.https.html Is a flaky text failure on iOS and macOS ToT and since introduced at 241244@main. HISTORY: https://results.webkit.org/?suite=layout-tests&test=http/wpt/cross-origin-opener-policy/non-secure-to-secure-context-navigation.https.html DIFF: @@ -1,3 +1,3 @@ -PASS Make sure that COOP causes a browsing context group switch when navigating from a secure context to a non-secure one +FAIL Make sure that COOP causes a browsing context group switch when navigating from a secure context to a non-secure one assert_true: Window should be closed expected true got false
Attachments
Radar WebKit Bug Importer
Comment 1 2022-09-02 16:41:03 PDT
Hercules Hjalmarsson
Comment 2 2022-09-02 16:44:49 PDT
This issue fails on 241321@main using command: run-webkit-tests -f --exit-after-n-failures 1 --force --child-processes=5 --ios-simulator --iterations=1000 http/wpt/cross-origin-opener-policy/non-secure-to-secure-context-navigation.https.html Unable to bisect builds prior to this.
EWS
Comment 3 2022-09-02 16:54:52 PDT
Test gardening commit 254120@main (23d253e825bb): <https://commits.webkit.org/254120@main> Reviewed commits have been landed. Closing PR #3977 and removing active labels.
Chris Dumez
Comment 4 2023-01-17 15:38:04 PST
EWS
Comment 5 2023-01-19 11:34:07 PST
Committed 259100@main (f5b11d420aca): <https://commits.webkit.org/259100@main> Reviewed commits have been landed. Closing PR #8739 and removing active labels.
Note You need to log in before you can comment on or make changes to this bug.