209480 2020-03-24 09:23:49 -0700 [ macOS wk1 ] webgl/2.0.0/conformance/attribs/gl-vertexattribpointer.html is flaky timing out 2021-03-18 00:50:17 -0700 1 1 1 Unclassified WebKit WebGL WebKit Nightly Build Unspecified Unspecified RESOLVED FIXED https://bugs.webkit.org/show_bug.cgi?id=208078 InRadar P2 Normal --- 214211 126404 222726 1 jacob_uphoff webkit-unassigned dino jonlee kbr kkinnunen webkit-bot-watchers-bugzilla webkit-bug-importer oldest_to_newest 1633332 0 jacob_uphoff 2020-03-24 09:23:49 -0700 webgl/2.0.0/conformance/attribs/gl-vertexattribpointer.html This test has been a flaky timeout since it was unskipped in r257283 on macOS wk1 debug. History: https://results.webkit.org/?suite=layout-tests&test=webgl%2F2.0.0%2Fconformance%2Fattribs%2Fgl-vertexattribpointer.html Diff: --- /Volumes/Data/slave/catalina-debug-tests-wk1/build/layout-test-results/webgl/2.0.0/conformance/attribs/gl-vertexattribpointer-expected.txt +++ /Volumes/Data/slave/catalina-debug-tests-wk1/build/layout-test-results/webgl/2.0.0/conformance/attribs/gl-vertexattribpointer-actual.txt @@ -1,3 +1,4 @@ +FAIL: Timed out waiting for notifyDone to be called This test runs the WebGL Test listed below in an iframe and reports PASS or FAIL. Test: ../../resources/webgl_test_files/conformance/attribs/gl-vertexattribpointer.html 1633333 1 webkit-bug-importer 2020-03-24 09:24:13 -0700 <rdar://problem/60827678> 1633356 2 jacob_uphoff 2020-03-24 09:41:35 -0700 Set expectations here: https://trac.webkit.org/changeset/258912/webkit 1676991 3 kbr 2020-07-31 15:12:39 -0700 James, could you please see whether this has been fixed by Bug 214211? 1722431 4 jonlee 2021-01-26 02:31:53 -0800 This appears to remain a flaky timeout on WK1 debug. 1722759 5 kbr 2021-01-26 15:54:13 -0800 This test seems to run very quickly, so it's strange that it would time out flakily in Debug builds. James is OOO for the moment; if this is urgent can anyone else investigate it? 1741065 6 kkinnunen 2021-03-18 00:50:17 -0700 Closing this one out. The test in general is a bit slow. The solution is to mark the test as Slow in TestExpectations. Later implementations could be sped up, but relative to other tests, this test probably will remain slowish.