173432 2017-06-15 13:57:28 -0700 Layout Test imported/w3c/web-platform-tests/fetch/api/policies/referrer-origin-worker.html is a flaky failure and crash. 2018-05-11 05:01:38 -0700 1 1 1 Unclassified WebKit New Bugs WebKit Nightly Build Unspecified Unspecified RESOLVED DUPLICATE 157068 https://bugs.webkit.org/show_bug.cgi?id=157068 P2 Normal --- 1 jlewis3 webkit-unassigned dbates Ms2ger ryanhaddad youennf oldest_to_newest 1319695 0 jlewis3 2017-06-15 13:57:28 -0700 imported/w3c/web-platform-tests/fetch/api/policies/referrer-origin-worker.html is a flaky failure and crash according to the flakiness dashboard. The crash occurs on Sierra Debug WK1, this is a previously documented bug (link in see also). The Flaky failures are on macOS Release Wk1 and on Sierra Debug WK1. https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=imported%2Fw3c%2Fweb-platform-tests%2Ffetch%2Fnosniff%2Fimportscripts.html https://build.webkit.org/results/Apple%20Sierra%20Release%20WK1%20(Tests)/r218346%20(2494)/results.html https://build.webkit.org/builders/Apple%20Sierra%20Release%20WK1%20(Tests)/builds/2494 I was able to reproduce the failure on Sierra Release WK1 with: run-webkit-tests imported/w3c/web-platform-tests/fetch/nosniff/importscripts.html -1 --iterations=100 -f --no-retry-failure The test is flaky and will not fail every time the test is run. I had to run it 2-3 times to fail. diff: --- /Volumes/Data/slave/sierra-release-tests-wk1/build/layout-test-results/imported/w3c/web-platform-tests/fetch/nosniff/importscripts-expected.txt +++ /Volumes/Data/slave/sierra-release-tests-wk1/build/layout-test-results/imported/w3c/web-platform-tests/fetch/nosniff/importscripts-actual.txt @@ -1,3 +1,5 @@ -PASS Test importScripts() +Harness Error (TIMEOUT), message = null +TIMEOUT Test importScripts() Test timed out + 1320159 1 jlewis3 2017-06-16 14:10:13 -0700 Marked test as flaky on Mac WK1 Debug: https://trac.webkit.org/changeset/218413/webkit 1423122 2 Ms2ger 2018-05-11 05:01:38 -0700 *** This bug has been marked as a duplicate of bug 157068 ***