New issue
Advanced search Search tips

Issue 727912 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

MSE conformance test related to Duration change 18, 69, 89 failed on all Chrome builds

Project Member Reported by yini...@chromium.org, May 30 2017

Issue description

Chrome Version: all
OS: all

I suspect these three tests are broken. They pass before on Chrome prior build but now they all failed even on old build.
Thom, can you take a look?

What steps will reproduce the problem?
(1) navigate to https://yt-dash-mse-test.commondatastorage.googleapis.com/unit-tests/tip.html?timestamp=1496180153311
(2) run tests: 18, 69, 89


What is the expected result?
all three tests pass

What happens instead?
all tests fail

 
Owner: yini...@chromium.org
This is a preemptive change to accommodate latest spec changes. Running Chrome with --enable-blink-features=MediaSourceNewAbortAndDuration will enable the latest spec change and the tests should pass.
It does pass after enable the feature. will you update test script to accomodate this feature change?
Status: WontFix (was: Assigned)
in order to run flag in c#1 in Mac, use below command in cmd window
open -a Google\ Chrome --args --enable-blink-features=MediaSourceNewAbortAndDuration
Owner: tdedecko@chromium.org
Status: Assigned (was: WontFix)
thom, in the present Chrome 63.0.3230.0, even start Chrome with --enable-blink-features=MediaSourceNewAbortAndDuration, these three tests still fail.
Is it possible a real bug? they used to pass in Chrome 61 after enable this feature.
Cc: wolenetz@chromium.org
Owner: yini...@chromium.org
Could be a real bug. I'm unfamiliar of changes in Chrome that would break this. Does this feature have a new flag for enabling it in Chrome?
Cc: -wolenetz@chromium.org
Owner: wolenetz@chromium.org
Matt, can you take a look?
to be specific, only test 69 (MediaSourceDurationVP9) failed after enable this feature (without enableing this feature, all 18, 69,89 fail). the test log shows as below. it seems onsourceclose event is not called so this test Time Out.
Please follow c#4 to enable the flag. Then run test #69 by navigating to test page https://yt-dash-mse-test.commondatastorage.googleapis.com/unit-tests/tip.html?timestamp=1496180153311

TestExecutor:  All tests are completed 
TestExecutor:  Test 69:MediaSourceDurationVP9 threw an error: Test 69:MediaSourceDurationVP9 TIMED OUT! 
MediaSourceDurationVP9:    0: (0, 181.580067) 
MediaSourceDurationVP9:  sb1.buffered.length 1 
MediaSourceDurationVP9:    0: (0, 5) 
MediaSourceDurationVP9:  sb0.buffered.length 1 
MediaSourceDurationVP9:  ms.sb count = 2 
MediaSourceDurationVP9:  video.networkState = 2 
MediaSourceDurationVP9:  video.readyState = 2 
MediaSourceDurationVP9:  video.currentTime = 7.985305 
TestExecutor:  Test 69:MediaSourceDurationVP9 STARTED with timeout 30000 
TestExecutor:  Media Source and Encrypted Media Conformance Tests (version 20171005191104-fLa1Vj20YEIaJqRQ) 
I'll take a look soon.

this bug still repro on chrome 64.0.3253.3
Status: WontFix (was: Assigned)
this bug not repro anymore in 64.0.3278.0

Sign in to add a comment