NEW 162523
[mac-sierra] LayoutTest imported/w3c/web-platform-tests/media-source/mediasource-preload.html is a flaky failure
https://bugs.webkit.org/show_bug.cgi?id=162523
Summary [mac-sierra] LayoutTest imported/w3c/web-platform-tests/media-source/mediasou...
Ryan Haddad
Reported 2016-09-23 17:12:58 PDT
LayoutTest imported/w3c/web-platform-tests/media-source/mediasource-preload.html is a flaky failure https://build.webkit.org/results/Apple%20Sierra%20Release%20WK2%20(Tests)/r206336%20(31)/results.html --- /Volumes/Data/slave/sierra-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/media-source/mediasource-preload-expected.txt +++ /Volumes/Data/slave/sierra-release-tests-wk2/build/layout-test-results/imported/w3c/web-platform-tests/media-source/mediasource-preload-actual.txt @@ -1,9 +1,11 @@ + +Harness Error (TIMEOUT), message = null PASS sourceopen occurs with element preload=auto PASS sourceopen occurs with element preload=metadata PASS sourceopen occurs with element preload=none -PASS error occurs with bogus blob URL (revoked MediaSource object URL) and element preload=auto -PASS error occurs with bogus blob URL (revoked MediaSource object URL) and element preload=metadata -PASS error occurs with bogus blob URL (corrupted MediaSource object URL) and element preload=auto -PASS error occurs with bogus blob URL (corrupted MediaSource object URL) and element preload=metadata +TIMEOUT error occurs with bogus blob URL (revoked MediaSource object URL) and element preload=auto Test timed out +TIMEOUT error occurs with bogus blob URL (revoked MediaSource object URL) and element preload=metadata Test timed out +TIMEOUT error occurs with bogus blob URL (corrupted MediaSource object URL) and element preload=auto Test timed out +TIMEOUT error occurs with bogus blob URL (corrupted MediaSource object URL) and element preload=metadata Test timed out
Attachments
Ryan Haddad
Comment 1 2016-09-23 17:20:07 PDT
Alexey Proskuryakov
Comment 2 2016-09-25 14:41:05 PDT
This test was updated and marked as a pass a few days ago; so looks like the fix didn'y quite work.
Note You need to log in before you can comment on or make changes to this bug.