Bug 123498 - REGRESSION (r167632): media/track/track-in-band-cues-added-once.html is failing
Summary: REGRESSION (r167632): media/track/track-in-band-cues-added-once.html is failing
Status: RESOLVED DUPLICATE of bug 132715
Alias: None
Product: WebKit
Classification: Unclassified
Component: Media (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-29 23:53 PDT by Ryosuke Niwa
Modified: 2014-11-17 13:54 PST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ryosuke Niwa 2013-10-29 23:53:50 PDT
http://webkit-test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=media%2Ftrack%2Ftrack-in-band-cues-added-once.html

It appears that this test has been failing since the Mavericks builders were added

e.g. http://build.webkit.org/results/Apple%20Mavericks%20Release%20WK2%20(Tests)/r158255%20(92)/results.html

--- /Volumes/Data/slave/mavericks-release-tests-wk2/build/layout-test-results/media/track/track-in-band-cues-added-once-expected.txt
+++ /Volumes/Data/slave/mavericks-release-tests-wk2/build/layout-test-results/media/track/track-in-band-cues-added-once-actual.txt
@@ -8,8 +8,8 @@
 ** Check initial in-band track states
 EXPECTED (video.textTracks.length == '1') OK
 RUN(inbandTrack1 = video.textTracks[0])
-EXPECTED (inbandTrack1.mode == 'disabled') OK
-EXPECTED (inbandTrack1.cues == 'null') OK
+EXPECTED (inbandTrack1.mode == 'disabled'), OBSERVED 'showing' FAIL
+EXPECTED (inbandTrack1.cues == 'null'), OBSERVED '[object TextTrackCueList]' FAIL
 EXPECTED (inbandTrack1.language == 'en') OK
 EXPECTED (inbandTrack1.kind == 'captions') OK
Comment 1 Alexey Proskuryakov 2014-04-22 23:05:40 PDT
This test was passing for a long time, and then it broke yesterday in <http://trac.webkit.org/r167632>.

The new diff is:

@@ -24,5 +24,10 @@
 EVENT(seeked)
 EXPECTED (inbandTrack1.cues.length > '0') OK
 RUN(video.pause())
+Found unexpected cue starting at 0.2 FAIL
+Found unexpected cue starting at 1.0008333333333332 FAIL
+Found unexpected cue starting at 1.0008333333333332 FAIL
+Found unexpected cue starting at 1.7682333333333333 FAIL
+Found unexpected cue starting at 1.7682333333333333 FAIL
 END OF TEST
Comment 2 Alexey Proskuryakov 2014-04-22 23:14:31 PDT
Correction: the test was flaky, and is now failing all the time.
Comment 3 Brent Fulgham 2014-05-08 16:38:30 PDT
Duplicate of Bug 132715.

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