NEW 204981
Flaky Test: webgl/1.0.3/conformance/ogles/GL/mat/mat_025_to_032.html 
https://bugs.webkit.org/show_bug.cgi?id=204981
Summary Flaky Test: webgl/1.0.3/conformance/ogles/GL/mat/mat_025_to_032.html
WebKit Commit Bot
Reported Saturday, December 7, 2019 9:27:33 AM UTC
This is an automatically generated bug from the commit-queue. webgl/1.0.3/conformance/ogles/GL/mat/mat_025_to_032.html has been flaky on the commit-queue. webgl/1.0.3/conformance/ogles/GL/mat/mat_025_to_032.html was authored by justin_fan@apple.com. https://trac.webkit.org/browser/trunk/LayoutTests/webgl/1.0.3/conformance/ogles/GL/mat/mat_025_to_032.html The commit-queue just saw webgl/1.0.3/conformance/ogles/GL/mat/mat_025_to_032.html flake (text diff) while processing attachment 385080 [details] on bug 204954. Bot: webkit-cq-03 Port: <class 'webkitpy.common.config.ports.MacPort'> Platform: Mac OS X 10.13.6 The bots will update this with information from each new failure. If you believe this bug to be fixed or invalid, feel free to close. The bots will re-open if the flake re-occurs. If you would like to track this test fix with another bug, please close this bug as a duplicate. The bots will follow the duplicate chain when making future comments.
Attachments
Archive of layout-test-results from webkit-cq-03 (3.47 MB, application/zip)
2019-12-07 01:27 PST, WebKit Commit Bot 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
WebKit Commit Bot
Comment 1 Saturday, December 7, 2019 9:27:34 AM UTC
Created attachment 385087 [details] Archive of layout-test-results from webkit-cq-03
Alexey Proskuryakov
Comment 2 Saturday, December 7, 2019 9:17:27 PM UTC
I don't see any failure in post-commit testing. @@ -1,5 +1,23 @@ This test runs the WebGL Test listed below in an iframe and reports PASS or FAIL. Test: ../../../../resources/webgl_test_files/conformance/ogles/GL/mat/mat_025_to_032.html -[ PASS ] All tests passed +[ 1: PASS ] images are the same +[ 2: PASS ] getError was expected value: NO_ERROR : there should be no errors +[ 3: PASS ] images are the same +[ 4: PASS ] getError was expected value: NO_ERROR : there should be no errors +[ 5: PASS ] images are the same +[ 6: PASS ] getError was expected value: NO_ERROR : there should be no errors +[ 7: PASS ] images are the same +[ 8: PASS ] getError was expected value: NO_ERROR : there should be no errors +[ 9: PASS ] images are the same +[ 10: PASS ] getError was expected value: NO_ERROR : there should be no errors +[ 11: FAIL ] pixel @ (169, 33 was [0,0,0,0] expected [255,255,255,255] +[ 12: FAIL ] images are different +[ 13: PASS ] getError was expected value: NO_ERROR : there should be no errors +[ 14: PASS ] images are the same +[ 15: PASS ] getError was expected value: NO_ERROR : there should be no errors +[ 16: PASS ] images are the same +[ 17: PASS ] getError was expected value: NO_ERROR : there should be no errors +[ 18: PASS ] successfullyParsed is true +[ FAIL ] 2 failures reported
Note You need to log in before you can comment on or make changes to this bug.