Created attachment 410697 [details] test list for reproduction Description: http/tests/in-app-browser-privacy/top-frame-redirect-to-non-app-bound-domain-blocked.html The first failure that I see this on the dashboard was 09/30/20 at r267785, but does not appear to be relevant to what would have caused this. I can reproduce this on r267763, but unable to reproduce on r267762 or earlier. Commit r267763 has to do with moving things on WebProcessPool associated with NetworkProcessProxy ownership and moves them to WebsiteDataStore, which could have introduced the constant failure. The change was introduced here https://trac.webkit.org/changeset/267763/webkit. REPRODUCTION STEPS Command: run-webkit-tests --ios-simulator --no-retry --force -f --iterations 10 --test-list testlist.txt Result: r268063 failure (ToT) r267786 failure r267785 failure r267784 failure r267763 failure r267762 pass r267761 pass Regressions: Unexpected text-only failures (3) http/tests/cookies/js-get-and-set-http-only-cookie.html [ Failure ] http/tests/download/inherited-encoding-form-submission-result.html [ Failure ] http/tests/in-app-browser-privacy/top-frame-redirect-to-non-app-bound-domain-blocked.html [ Failure ] History: https://results.webkit.org/?platform=ios&limit=50000&suite=layout-tests&test=http%2Ftests%2Fin-app-browser-privacy%2Ftop-frame-redirect-to-non-app-bound-domain-blocked.html Diff Log: --- /Volumes/Data/Builds/build-267763/layout-test-results/http/tests/in-app-browser-privacy/top-frame-redirect-to-non-app-bound-domain-blocked-expected.txt +++ /Volumes/Data/Builds/build-267763/layout-test-results/http/tests/in-app-browser-privacy/top-frame-redirect-to-non-app-bound-domain-blocked-actual.txt @@ -1,10 +1 @@ -Test top frame redirects block non-app-bound domains - -On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE". - - -PASS Redirect to non app-bound domain failed -PASS successfullyParsed is true - -TEST COMPLETE - +FAILED: Should not have loaded
<rdar://problem/70019001>
*** This bug has been marked as a duplicate of bug 217386 ***