Bug 124931 - [EFL] media/track/audio/audio-track-mkv-vorbis-enabled.html is flaky
Summary: [EFL] media/track/audio/audio-track-mkv-vorbis-enabled.html is flaky
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit EFL (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-27 05:34 PST by Michal Pakula vel Rutka
Modified: 2017-03-11 10:35 PST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michal Pakula vel Rutka 2013-11-27 05:34:38 PST
Layout test media/track/audio/audio-track-mkv-vorbis-enabled.html is flaky probably since it was introduced in r158436 <http://trac.webkit.org/changeset/158436>. First flakiness occurred in r158467 build.

http://webkit-test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=media%2Ftrack%2Faudio%2Faudio-track-mkv-vorbis-enabled.html

Test output:
--- /mnt/buildbot/efl-linux-slave-2/efl-linux-64-release-wk2/build/layout-test-results/media/track/audio/audio-track-mkv-vorbis-enabled-expected.txt
+++ /mnt/buildbot/efl-linux-slave-2/efl-linux-64-release-wk2/build/layout-test-results/media/track/audio/audio-track-mkv-vorbis-enabled-actual.txt
@@ -6,12 +6,12 @@
 RUN(track2 = video.audioTracks[1])
 
 ** Checking initial state
-EXPECTED (track1.enabled == 'true') OK
+EXPECTED (track1.enabled == 'true'), OBSERVED 'false' FAIL
 EXPECTED (track2.enabled == 'false') OK
 
 ** Ensuring we can have two enabled tracks
 RUN(track2.enabled = true)
-EXPECTED (track1.enabled == 'true') OK
+EXPECTED (track1.enabled == 'true'), OBSERVED 'false' FAIL
 EXPECTED (track2.enabled == 'true') OK
 
 ** Ensuring we can have zero enabled tracks
Comment 1 Michael Catanzaro 2017-03-11 10:35:59 PST
Closing this bug because the EFL port has been removed from trunk.

If you feel this bug applies to a different upstream WebKit port and was closed in error, please either update the title and reopen the bug, or leave a comment to request this.