Bug 182818

Summary: Flaky Test: media/modern-media-controls/status-label/status-label-font.html
Product: WebKit Reporter: WebKit Commit Bot <commit-queue>
Component: Tools / TestsAssignee: WebKit Commit Bot <commit-queue>
Status: NEW    
Severity: Normal CC: graouts, jlewis3, lforschler, mcatanzaro, ryanhaddad
Priority: P2    
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=171828
Bug Depends on:    
Bug Blocks: 50856    
Attachments:
Description Flags
Archive of layout-test-results from webkit-cq-01 none

WebKit Commit Bot
Reported 2018-02-14 19:37:56 PST
This is an automatically generated bug from the commit-queue. media/modern-media-controls/status-label/status-label-font.html has been flaky on the commit-queue. media/modern-media-controls/status-label/status-label-font.html was authored by graouts@apple.com, mcatanzaro@igalia.com, and ryanhaddad@apple.com. https://trac.webkit.org/browser/trunk/LayoutTests/media/modern-media-controls/status-label/status-label-font.html The commit-queue just saw media/modern-media-controls/status-label/status-label-font.html flake (DumpRenderTree crashed) while processing attachment 333866 [details] on bug 182817. Bot: webkit-cq-01 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-01 (2.23 MB, application/zip)
2018-02-14 19:37 PST, WebKit Commit Bot 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
WebKit Commit Bot
Comment 1 2018-02-14 19:37:57 PST
Created attachment 333870 [details] Archive of layout-test-results from webkit-cq-01
Note You need to log in before you can comment on or make changes to this bug.