http/tests/misc/iframe-shadow-realm.html Is a constant timeout on iOS16 and macOS wk2 ToT and since 254483@main. It appears that it was expected to fail after 254483@main. However, it wasn't expected to timeout judging by the expectations set. HISTORY: https://results.webkit.org/?suite=layout-tests&test=http/tests/misc/iframe-shadow-realm.html DIFF: @@ -1,10 +1,9 @@ +CONSOLE MESSAGE: Unhandled Promise Rejection: ReferenceError: Can't find variable: ShadowRealm +FAIL: Timed out waiting for notifyDone to be called + Test that shadow realms can load modules from different-origin iframe contexts On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE". -PASS event.data is 42 -PASS successfullyParsed is true -TEST COMPLETE -
<rdar://problem/100414380>
This issue can be bisected to 254483@main using command: run-webkit-tests --iterations=2 --ios-simulator http/tests/misc/iframe-shadow-realm.html
Test gardening commit 254869@main (a7f739402edf): <https://commits.webkit.org/254869@main> Reviewed commits have been landed. Closing PR #4713 and removing active labels.
This is probably just fall out for disabling ShadowRealm. All we need to do for this test is add this at the top of the file: <!-- webkit-test-runner [ jscOptions=--useShadowRealm=true ] -->
Yusuke tells me that this test as currently written can timeout. So, this is expected behavior.
Test gardening commit 254957@main (a53a5529e983): <https://commits.webkit.org/254957@main> Reviewed commits have been landed. Closing PR #4795 and removing active labels.
FYI, skipping the test is the right thing to do here (which Hercules just landed a patch for) because a test expectation of [Pass Fail Timeout] gives us no information, and wastes EWS time with time outs.