Summary: | REGRESSION: [ Mojave Debug wk1 ] webgl/1.0.3/conformance/rendering/many-draw-calls.html is Timing out | ||
---|---|---|---|
Product: | WebKit | Reporter: | Truitt Savell <tsavell> |
Component: | WebGL | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED INVALID | ||
Severity: | Normal | CC: | ap, dino, jlewis3, ryanhaddad, webkit-bot-watchers-bugzilla, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
See Also: |
https://bugs.webkit.org/show_bug.cgi?id=182144 https://bugs.webkit.org/show_bug.cgi?id=205668 |
Description
Truitt Savell
2019-12-18 14:13:34 PST
Diff showed --- /Volumes/Data/slave/mojave-debug-tests-wk1/build/layout-test-results/webgl/1.0.3/conformance/rendering/many-draw-calls-expected.txt +++ /Volumes/Data/slave/mojave-debug-tests-wk1/build/layout-test-results/webgl/1.0.3/conformance/rendering/many-draw-calls-actual.txt @@ -1,5 +1,14 @@ +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/rendering/many-draw-calls.html -[ PASS ] All tests passed +[ 1: PASS ] Completed 10 iterations +[ 2: PASS ] Completed 20 iterations +[ 3: PASS ] Completed 30 iterations +[ 4: PASS ] Completed 40 iterations +[ 5: PASS ] Completed 50 iterations +[ 6: PASS ] Completed 60 iterations +[ 7: PASS ] Completed 70 iterations +[ 8: PASS ] Completed 80 iterations +[ 9: PASS ] Completed 90 iterations I was unable to reproduce this on my system at this time. marked test as timeout while it is investigated in https://trac.webkit.org/changeset/253753/webkit This test is already tracked in bug 182144, where it got skipped. Must be re-enabled in a more specific TestExpectation I guess? It is skipped here: LayoutTests/platform/ios-wk2/TestExpectations:1234:webkit.org/b/182144 [ Debug ] webgl/1.0.3/conformance/rendering/many-draw-calls.html [ Skip ] This test was just getting gradually slower, until it started to time out. Mojave bots still need to be rebooted every couple weeks, could it be that we forgot to? I just rebooted them all, let's see if that helps. But also, there is an ANGLE regression on the same test, so it will be hard to tell. This test passes again after rebooting and reverting ANGLE. So I think that this is just about the OS getting slower with time, and we need to keep rebooting High sierra and Mojave bots periodically. |