REOPENED 187476
Layout Test media/video-background-playback.html is flaky 
https://bugs.webkit.org/show_bug.cgi?id=187476
Summary Layout Test media/video-background-playback.html is flaky
Truitt Savell
Reported 2018-07-09 09:52:48 PDT
The following layout test is flaky on Sierra and High Sierra media/video-background-playback.html Probable cause: I do not know Flakiness Dashboard: https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=media%2Fvideo-background-playback.html
Attachments
Mark as flaky (1.37 KB, patch)
2018-07-09 09:59 PDT, Truitt Savell 		ews-watchlist: commit-queue-
DetailsFormatted DiffDiff
Archive of layout-test-results from ews206 for win-future (12.85 MB, application/zip)
2018-07-09 13:59 PDT, EWS Watchlist 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Truitt Savell
Comment 1 2018-07-09 09:59:02 PDT
Created attachment 344595 [details] Mark as flaky
WebKit Commit Bot
Comment 2 2018-07-09 12:30:18 PDT
Comment on attachment 344595 [details] Mark as flaky Clearing flags on attachment: 344595 Committed r233653: <https://trac.webkit.org/changeset/233653>
WebKit Commit Bot
Comment 3 2018-07-09 12:30:19 PDT
All reviewed patches have been landed. Closing bug.
Radar WebKit Bug Importer
Comment 4 2018-07-09 12:31:29 PDT
<rdar://problem/41984705>
Ryan Haddad
Comment 5 2018-07-09 12:45:20 PDT
Reopening to track investigation.
EWS Watchlist
Comment 6 2018-07-09 13:58:51 PDT
Comment on attachment 344595 [details] Mark as flaky Attachment 344595 [details] did not pass win-ews (win): Output: https://webkit-queues.webkit.org/results/8484897 New failing tests: http/tests/security/contentSecurityPolicy/userAgentShadowDOM/allow-audio.html
EWS Watchlist
Comment 7 2018-07-09 13:59:03 PDT
Created attachment 344613 [details] Archive of layout-test-results from ews206 for win-future The attached test failures were seen while running run-webkit-tests on the win-ews. Bot: ews206 Port: win-future Platform: CYGWIN_NT-6.1-2.9.0-0.318-5-3-x86_64-64bit
Note You need to log in before you can comment on or make changes to this bug.