Bug 187618

Summary: REGRESSION: [iOS] Layout Test media/media-fullscreen-pause-inline.html is a flaky failure
Product: WebKit Reporter: Ryan Haddad <ryanhaddad>
Component: New BugsAssignee: Peng Liu <peng.liu6>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: ap, jeremyj-wk, jer.noble, peng.liu6, realdawei, tsavell, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: Other   
Hardware: Unspecified   
OS: Unspecified   

Description Ryan Haddad 2018-07-12 14:36:56 PDT
The following layout test is flaky on iOS simulator

media/media-fullscreen-pause-inline.html

Probable cause:

Unknown. The dashboard suggests that this may have started around r233540 on 7/5/18.

Flakiness Dashboard:

https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=media%2Fmedia-fullscreen-pause-inline.html

--- /Volumes/Data/slave/ios-simulator-11-release-tests-wk2/build/layout-test-results/media/media-fullscreen-pause-inline-expected.txt
+++ /Volumes/Data/slave/ios-simulator-11-release-tests-wk2/build/layout-test-results/media/media-fullscreen-pause-inline-actual.txt
@@ -13,6 +13,6 @@
 EVENT(pause)
 EXPECTED (video.paused == 'true') OK
 RUN(video.play().then(playingAgain))
-EXPECTED (video.webkitDisplayingFullscreen == 'true') OK
+EXPECTED (video.webkitDisplayingFullscreen == 'true'), OBSERVED 'false' FAIL
 END OF TEST
Comment 1 Alexey Proskuryakov 2018-07-17 11:25:48 PDT
Can the regression point be confirmed with local testing?
Comment 2 Ryan Haddad 2018-07-17 11:29:35 PDT
(In reply to Alexey Proskuryakov from comment #1)
> Can the regression point be confirmed with local testing?
We will give it a shot.
Comment 3 Ryan Haddad 2018-10-22 17:51:29 PDT
I can reproduce this with:
run-webkit-tests --ios-simulator media/media-fullscreen-pause-inline.html --iter 100 --no-retry
Comment 4 Ryan Haddad 2018-10-22 17:53:09 PDT
Marked test as flaky in http://trac.webkit.org/r237345
Comment 5 Radar WebKit Bug Importer 2018-10-22 17:53:34 PDT
<rdar://problem/45472902>
Comment 6 Peng Liu 2020-05-11 14:16:16 PDT

*** This bug has been marked as a duplicate of bug 211645 ***