RESOLVED DUPLICATE of bug 211645 193399
REGRESSION: Layout Test media/media-fullscreen-return-to-inline.html is a flaky timeout
https://bugs.webkit.org/show_bug.cgi?id=193399
Summary REGRESSION: Layout Test media/media-fullscreen-return-to-inline.html is a fla...
Truitt Savell
Reported 2019-01-14 09:16:48 PST
The following layout test is failing on MacOS media/media-fullscreen-return-to-inline.html Probable cause: This test recently became a flakey failure. It is highly intermittent and has no clear regression point. First failure came from a run of r239860. Flakiness Dashboard: https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=media%2Fmedia-fullscreen-return-to-inline.html Diff: --- /Volumes/Data/slave/highsierra-release-tests-wk2/build/layout-test-results/media/media-fullscreen-return-to-inline-expected.txt +++ /Volumes/Data/slave/highsierra-release-tests-wk2/build/layout-test-results/media/media-fullscreen-return-to-inline-actual.txt @@ -12,6 +12,6 @@ EVENT(webkitfullscreenchange) RUN(video.webkitExitFullscreen()) EVENT(webkitfullscreenchange) -EXPECTED (video.paused == 'false') OK +EXPECTED (video.paused == 'false'), OBSERVED 'true' FAIL END OF TEST
Attachments
Truitt Savell
Comment 1 2019-01-23 11:47:55 PST
the behavior of this test seems to have changed around 1/17 around r240124. the test is not timing out with around the same frequency as the failures. the test is no longer failing.
Truitt Savell
Comment 2 2019-02-04 09:15:07 PST
This test timeout is reproducible with command: run-webkit-tests --root testbuild-240924 media/media-fullscreen-return-to-inline.html --iterations 500 -f
Radar WebKit Bug Importer
Comment 3 2019-02-12 11:23:28 PST
Ryan Haddad
Comment 4 2019-03-11 14:56:33 PDT
This is still timing out quite frequently on the bots, so we should consider updating TestExpectations.
Truitt Savell
Comment 5 2019-03-11 15:48:26 PDT
Peng Liu
Comment 6 2020-05-11 14:15:50 PDT
*** This bug has been marked as a duplicate of bug 211645 ***
Note You need to log in before you can comment on or make changes to this bug.