202939 2019-10-14 13:17:18 -0700 [ Windows ] Layout Test fast/workers/worker-exception-during-navigation.html is flaky 2024-08-27 18:38:00 -0700 1 1 1 Unclassified WebKit Tools / Tests WebKit Nightly Build Unspecified Unspecified RESOLVED DUPLICATE 102131 InRadar P2 Normal --- 1 tsavell webkit-unassigned fujii webkit-bot-watchers-bugzilla webkit-bug-importer oldest_to_newest 1579758 0 tsavell 2019-10-14 13:17:18 -0700 The following layout test is flaky on Win10 fast/workers/worker-exception-during-navigation.html Probable cause: This has been flakey for the whole history Flakiness Dashboard: https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=fast%2Fworkers%2Fworker-exception-during-navigation.html Diff: --- /home/buildbot/worker/win10-release-tests/build/layout-test-results/fast/workers/worker-exception-during-navigation-expected.txt +++ /home/buildbot/worker/win10-release-tests/build/layout-test-results/fast/workers/worker-exception-during-navigation-actual.txt @@ -1,5 +1,11 @@ CONSOLE MESSAGE: line 27: Creating the workers. CONSOLE MESSAGE: line 44: Unloading the current document to see if there will be a crash. +CONSOLE MESSAGE: line 31: Cannot load worker-exception.js due to access control checks. +CONSOLE MESSAGE: line 31: Cannot load worker-exception.js due to access control checks. +CONSOLE MESSAGE: line 31: Cannot load worker-exception.js due to access control checks. +CONSOLE MESSAGE: line 31: Cannot load worker-exception.js due to access control checks. +CONSOLE MESSAGE: line 31: Cannot load worker-exception.js due to access control checks. +CONSOLE MESSAGE: line 31: Cannot load worker-exception.js due to access control checks. CONSOLE MESSAGE: line 12: No crashes: PASSED! The regression test for Bug 99658 1579800 1 webkit-bug-importer 2019-10-14 14:00:18 -0700 <rdar://problem/56262308> 1579820 2 tsavell 2019-10-14 14:21:43 -0700 Marked this test as failing as part of: https://trac.webkit.org/changeset/251098/webkit 2055795 3 fujii 2024-08-27 18:38:00 -0700 *** This bug has been marked as a duplicate of bug 102131 ***