RESOLVED DUPLICATE of bug 206225 168092
REGRESSION: LayoutTest media/track/track-cues-sorted-before-dispatch.html is a flaky failure
https://bugs.webkit.org/show_bug.cgi?id=168092
Summary REGRESSION: LayoutTest media/track/track-cues-sorted-before-dispatch.html is ...
Ryan Haddad
Reported 2017-02-09 16:53:17 PST
LayoutTest media/track/track-cues-sorted-before-dispatch.html is a flaky failure https://build.webkit.org/results/Apple%20El%20Capitan%20Debug%20WK1%20(Tests)/r211996%20(11445)/results.html https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=media%2Ftrack%2Ftrack-cues-sorted-before-dispatch.html --- /Volumes/Data/slave/elcapitan-debug-tests-wk1/build/layout-test-results/media/track/track-cues-sorted-before-dispatch-expected.txt +++ /Volumes/Data/slave/elcapitan-debug-tests-wk1/build/layout-test-results/media/track/track-cues-sorted-before-dispatch-actual.txt @@ -9,8 +9,8 @@ Cue event: enter id: 3 time: 5.1 Cue event: enter id: 2 time: 5.1 Cue event: enter id: 4 time: 5.1 +Cue event: exit id: 4 time: 5.101 Cue event: exit id: 2 time: 5.101 -Cue event: exit id: 4 time: 5.101 Cue event: enter id: 5 time: 5.3 Cue event: exit id: 3 time: 5.301 Cue event: exit id: 1 time: 5.8
Attachments
Ryan Haddad
Comment 1 2017-02-09 16:56:13 PST
First failure on macOS on the flakiness dashboard was 1/23/2017 4:04:08 AM @ r211037
Matt Lewis
Comment 2 2017-05-30 14:13:39 PDT
I was able to reproduce the failure on Sierra with: run-webkit-tests media/track/track-cues-sorted-before-dispatch.html --no-retry-failure --iterations=100 -f --debug Also tested this with revision older than previously stated (used r211020) and failure occurred on that revision as well. Failure is most likely older than previously thought.
Matt Lewis
Comment 3 2017-06-27 11:17:41 PDT
The test has now become very flaky on iOS simulator WK2. The diff is the same. The test run time is generally the same on passes and failures on iOS Simulator. The test has also failed on El Capitan as well.
Matt Lewis
Comment 4 2017-07-03 14:44:58 PDT
Alexey Proskuryakov
Comment 5 2020-01-17 23:19:04 PST
This was probably fixed by bug 206225, let's confirm in a couple days and remove the expectation.
Alexey Proskuryakov
Comment 6 2020-01-25 18:41:06 PST
This issue was indeed fixed. I see a less frequent failure on this test on internal bots that is different though. We'll need a separate bug to track that. *** This bug has been marked as a duplicate of bug 206225 ***
Note You need to log in before you can comment on or make changes to this bug.