Bug 191991

Summary: Flaky Test: webgl/2.0.0/conformance2/rendering/blitframebuffer-filter-outofbounds.html
Product: WebKit Reporter: WebKit Commit Bot <commit-queue>
Component: Tools / TestsAssignee: WebKit Commit Bot <commit-queue>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: jlewis3, justin_fan, lforschler, ryanhaddad, tsavell
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 50856    
Attachments:
Description Flags
Archive of layout-test-results from webkit-cq-02 none

WebKit Commit Bot
Reported 2018-11-26 18:25:59 PST
This is an automatically generated bug from the commit-queue. webgl/2.0.0/conformance2/rendering/blitframebuffer-filter-outofbounds.html has been flaky on the commit-queue. webgl/2.0.0/conformance2/rendering/blitframebuffer-filter-outofbounds.html was authored by justin_fan@apple.com. https://trac.webkit.org/browser/trunk/LayoutTests/webgl/2.0.0/conformance2/rendering/blitframebuffer-filter-outofbounds.html The commit-queue just saw webgl/2.0.0/conformance2/rendering/blitframebuffer-filter-outofbounds.html flake (DumpRenderTree crashed) while processing attachment 355698 [details] on bug 190923. Bot: webkit-cq-02 Port: <class 'webkitpy.common.config.ports.MacPort'> Platform: Mac OS X 10.12.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-02 (2.56 MB, application/zip)
2018-11-26 18:26 PST, WebKit Commit Bot
no flags
WebKit Commit Bot
Comment 1 2018-11-26 18:26:01 PST
Created attachment 355700 [details] Archive of layout-test-results from webkit-cq-02
Alexey Proskuryakov
Comment 2 2018-12-01 16:07:20 PST
*** This bug has been marked as a duplicate of bug 192050 ***
Note You need to log in before you can comment on or make changes to this bug.