Closed
Bug 1116644
Opened 9 years ago
Closed 9 years ago
MSE Compliance Test: Fail test 19: TimestampOffsetVideo
Categories
(Core :: Audio/Video, defect, P3)
Core
Audio/Video
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jya, Unassigned)
References
Details
TestRunner: All tests are completed TestRunner: Longest test is TimestampOffsetAudio, it takes 0.027933333333333334 of its timeout. TestRunner: Finished! TestRunner: TestRunner.prototype.error@http://yt-dash-mse-test.commondatastorage.googleapis.com/unit-tests/js/harness/test-20141211110536.js:410:9 TestRunner.prototype.assert@http://yt-dash-mse-test.commondatastorage.googleapis.com/unit-tests/js/harness/test-20141211110536.js:180:5 TestRunner.prototype.check@http://yt-dash-mse-test.commondatastorage.googleapis.com/unit-tests/js/harness/test-20141211110536.js:197:5 TestRunner.prototype.checkEq@http://yt-dash-mse-test.commondatastorage.googleapis.com/unit-tests/js/harness/test-20141211110536.js:211:1 ConformanceTest/createTimestampOffsetTest/test.prototype.onsourceopen/xhr</<@http://yt-dash-mse-test.commondatastorage.googleapis.com/unit-tests/js/tests/2015/conformanceTest-20141211110536.js:330:1 TimestampOffsetVideo: 0: (0.083333, 1.125) TimestampOffsetVideo: sb0.buffered.length 1 TimestampOffsetVideo: ms.sb count = 1 TimestampOffsetVideo: video.networkState = 2 TimestampOffsetVideo: video.readyState = 0 TimestampOffsetVideo: video.currentTime = 0 TestRunner: Assert failed: Range start is (0.083333) which should be (5) TestRunner: checkEq passed: Source buffer number is (1). TestRunner: checkNE passed: request index is (0). TestRunner: checkEq passed: XHR requestType is (GET). TestRunner: checkEq passed: request index is (-1). TimestampOffsetVideo: MS test started TestRunner: Starting test 19:TimestampOffsetVideo with timeout 30000
Reporter | ||
Comment 1•9 years ago
|
||
The 0.083333 range start comes from the MP4 sample (See bug 1113370)
See Also: → 1113370
Comment 2•9 years ago
|
||
Yeah so with my patches in bug 1064128, this test _almost_ passes, except we get 5.083333 instead of 5. We should bug google to fix their tests.
Updated•9 years ago
|
Priority: -- → P2
Updated•9 years ago
|
Priority: P2 → P3
Comment 3•9 years ago
|
||
This seems to be fixed. TestRunner: All tests are completed TestRunner: Longest test is TimestampOffsetVideo, it takes 0.0017333333333333333 of its timeout. TestRunner: Finished! TestRunner: New longest test TimestampOffsetVideo with timeout 30000 takes 52 TestRunner: Test TimestampOffsetVideo succeeded. TestRunner: checkApproxEq passed: Range end is (6.041667). TestRunner: checkEq passed: Range start is (5). TestRunner: checkEq passed: Source buffer number is (1). TestRunner: checkNE passed: request index is (0). TestRunner: checkEq passed: XHR requestType is (GET). TestRunner: checkEq passed: request index is (-1). TimestampOffsetVideo: MS test started TestRunner: Starting test 19:TimestampOffsetVideo with timeout 30000 TestRunner: Media Source and Encrypted Media Conformance Tests (version 20150326133122-e5cOEaP8ocqTCH34)
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•