The following layout test is a flaky timeout after the changes landed in r251067: http/tests/workers/service/registration-clear-redundant-worker.html Test History: https://results.webkit.org/?suite=layout-tests&suite=layout-tests&test=http%2Ftests%2Fsecurity%2FmixedContent%2Finsecure-image-in-iframe.html&test=http%2Ftests%2Fworkers%2Fservice%2Fregistration-clear-redundant-worker.html Diff: --- /Volumes/Data/slave/ios-simulator-13-release-tests-wk2/build/layout-test-results/http/tests/workers/service/registration-clear-redundant-worker-expected.txt +++ /Volumes/Data/slave/ios-simulator-13-release-tests-wk2/build/layout-test-results/http/tests/workers/service/registration-clear-redundant-worker-actual.txt @@ -1,6 +1,5 @@ -PASS: Unregistration was successful -PASS: Worker became redundant after unregistering -PASS: registration.installing is null -PASS: registration.waiting is null -PASS: registration.active is null +#PID UNRESPONSIVE - WebKitTestRunnerApp (pid 68680) +FAIL: Timed out waiting for notifyDone to be called +#EOF +#EOF
<rdar://problem/56480245>
Created attachment 381482 [details] Test List Test list for local reproduction.
Steps to Reproduce: Test appears timeout consistently when running the following command: run-webkit-tests --ios-simulator --no-retry -g --no-sample-on-timeout --test-list test-list.txt --child-process 1 See test-list.txt attachment.
(In reply to Russell Epstein from comment #0) > > Test History: > > https://results.webkit.org/?suite=layout-tests&suite=layout- > tests&test=http%2Ftests%2Fsecurity%2FmixedContent%2Finsecure-image-in-iframe. > html&test=http%2Ftests%2Fworkers%2Fservice%2Fregistration-clear-redundant- > worker.html Accidentally included extra test in history link. Updated Link: https://results.webkit.org/?suite=layout-tests&test=http%2Ftests%2Fworkers%2Fservice%2Fregistration-clear-redundant-worker.html
Marked test as a flaky timeout in r251397
Thanks for the repro steps, that is really helpful! I think I found the issue and will it as bug 203410.
*** This bug has been marked as a duplicate of bug 203410 ***