The test imported/w3c/web-platform-tests/html/webappapis/timers/type-long-setinterval.html is a flaky failure on both macOS wk2 debug builds. The first failure on Sierra was on 4/16/2017 https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=imported%2Fw3c%2Fweb-platform-tests%2Fhtml%2Fwebappapis%2Ftimers%2Ftype-long-setinterval.html https://build.webkit.org/results/Apple%20Sierra%20Debug%20WK2%20(Tests)/r216768%20(966)/results.html https://build.webkit.org/builders/Apple%20Sierra%20Debug%20WK2%20(Tests)/builds/966 diff --- /Volumes/Data/slave/sierra-debug-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/html/webappapis/timers/type-long-setinterval-expected.txt +++ /Volumes/Data/slave/sierra-debug-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/html/webappapis/timers/type-long-setinterval-actual.txt @@ -1,3 +1,4 @@ +CONSOLE MESSAGE: line 2448: Error: assert_unreached: Reached unreachable code PASS Type long timeout for setInterval
I was able to reproduce on Sierra Debug with: run-webkit-tests imported/w3c/web-platform-tests/html/webappapis/timers/type-long-setinterval.html --iterations=100 --no-retry-failure -f --debug -g
The original addition of this test was in: https://trac.webkit.org/changeset/215164/webkit
This has since started on WK1 as well as iOS. WK1: https://build.webkit.org/builders/Apple%20El%20Capitan%20Debug%20WK1%20(Tests)/builds/3432 https://build.webkit.org/results/Apple%20El%20Capitan%20Debug%20WK1%20(Tests)/r221639%20(3432)/results.html iOS: https://build.webkit.org/builders/Apple%20iOS%2010%20Simulator%20Release%20WK2%20(Tests)/builds/4204 https://build.webkit.org/results/Apple%20iOS%2010%20Simulator%20Release%20WK2%20(Tests)/r221798%20(4204)/results.html
Marked test as flaky: https://trac.webkit.org/changeset/221924/webkit
<rdar://problem/42792998>
*** Bug 207060 has been marked as a duplicate of this bug. ***
The test was renamed to type-long-setinterval.any.html and the test expectation was not updated. To me that is evidence that this is no longer an issue, so I'll close this one. Please reopen if type-long-setinterval.any.html starts having issues though.
(In reply to Martin Robinson from comment #7) > The test was renamed to type-long-setinterval.any.html and the test > expectation was not updated. To me that is evidence that this is no longer > an issue, so I'll close this one. Please reopen if > type-long-setinterval.any.html starts having issues though. On further inspection it seems that this test was converted into a JavaScript test during a WPT import and is no longer run.