Closed Bug 1113717 Opened 10 years ago Closed 9 years ago

Intermittent test_getUserMedia_stopVideoStreamWithFollowupVideo.html | Unexpected callback with = 'ended event never fired' at: ["@http://mochi.test:8888/tests/dom/media/tests/mochitest/test_getUserMedia_stopVideoStreamWithFollowupVideo.html:44:1",""]

Categories

(Core :: WebRTC: Audio/Video, defect, P3)

x86
Linux
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: RyanVM, Unassigned)

References

Details

(Keywords: intermittent-failure)

06:57:31 INFO - 123 INFO TEST-START | dom/media/tests/mochitest/test_getUserMedia_stopVideoStreamWithFollowupVideo.html 06:57:32 INFO - -*-*- UserCustomizations (parent): document created: http://mochi.test:8888/tests/dom/media/tests/mochitest/test_getUserMedia_stopVideoStreamWithFollowupVideo.html 06:57:32 INFO - -*-*- UserCustomizations (parent): _injectInWindow 06:57:32 INFO - -*-*- UserCustomizations (parent): principal status: 0 06:57:32 INFO - TEST DEVICES: Using media devices: 06:57:32 INFO - audio: Sine source at 440 Hz 06:57:32 INFO - video: Dummy video device 06:57:32 INFO - State time can't go backward 4208512 < 4209024. 06:58:02 INFO - 124 INFO TEST-PASS | dom/media/tests/mochitest/test_getUserMedia_stopVideoStreamWithFollowupVideo.html | A valid string reason is expected 06:58:02 INFO - 125 INFO TEST-PASS | dom/media/tests/mochitest/test_getUserMedia_stopVideoStreamWithFollowupVideo.html | Reason cannot be empty 06:58:02 INFO - 126 INFO Call getUserMedia for {"video":true} 06:58:02 INFO - 127 INFO TEST-PASS | dom/media/tests/mochitest/test_getUserMedia_stopVideoStreamWithFollowupVideo.html | Stream should be a LocalMediaStream 06:58:02 INFO - 128 INFO TEST-PASS | dom/media/tests/mochitest/test_getUserMedia_stopVideoStreamWithFollowupVideo.html | Before starting the media element, currentTime = 0 06:58:02 INFO - 129 INFO TEST-FAIL | dom/media/tests/mochitest/test_getUserMedia_stopVideoStreamWithFollowupVideo.html | The author of the test has indicated that flaky timeouts are expected. Reason: WebRTC inherently depends on timeouts 06:58:02 INFO - 130 INFO TEST-PASS | dom/media/tests/mochitest/test_getUserMedia_stopVideoStreamWithFollowupVideo.html | Media element should be playing 06:58:02 INFO - 131 INFO TEST-PASS | dom/media/tests/mochitest/test_getUserMedia_stopVideoStreamWithFollowupVideo.html | Duration should be infinity 06:58:02 INFO - 132 INFO TEST-PASS | dom/media/tests/mochitest/test_getUserMedia_stopVideoStreamWithFollowupVideo.html | Ready state shall be HAVE_ENOUGH_DATA or HAVE_CURRENT_DATA 06:58:02 INFO - 133 INFO TEST-PASS | dom/media/tests/mochitest/test_getUserMedia_stopVideoStreamWithFollowupVideo.html | Seekable length shall be zero 06:58:02 INFO - 134 INFO TEST-PASS | dom/media/tests/mochitest/test_getUserMedia_stopVideoStreamWithFollowupVideo.html | Buffered length shall be zero 06:58:02 INFO - 135 INFO TEST-PASS | dom/media/tests/mochitest/test_getUserMedia_stopVideoStreamWithFollowupVideo.html | MediaElement is not seekable with MediaStream 06:58:02 INFO - 136 INFO TEST-PASS | dom/media/tests/mochitest/test_getUserMedia_stopVideoStreamWithFollowupVideo.html | Start offset time shall not be a number 06:58:02 INFO - 137 INFO TEST-PASS | dom/media/tests/mochitest/test_getUserMedia_stopVideoStreamWithFollowupVideo.html | Loop shall be false 06:58:02 INFO - 138 INFO TEST-PASS | dom/media/tests/mochitest/test_getUserMedia_stopVideoStreamWithFollowupVideo.html | Preload should not exist 06:58:02 INFO - 139 INFO TEST-PASS | dom/media/tests/mochitest/test_getUserMedia_stopVideoStreamWithFollowupVideo.html | No src should be defined 06:58:02 INFO - 140 INFO TEST-PASS | dom/media/tests/mochitest/test_getUserMedia_stopVideoStreamWithFollowupVideo.html | Current src should still be an empty string 06:58:02 INFO - 141 INFO TEST-FAIL | dom/media/tests/mochitest/test_getUserMedia_stopVideoStreamWithFollowupVideo.html | The author of the test has indicated that flaky timeouts are expected. Reason: WebRTC inherently depends on timeouts 06:58:02 INFO - 142 INFO TEST-FAIL | dom/media/tests/mochitest/test_getUserMedia_stopVideoStreamWithFollowupVideo.html | The author of the test has indicated that flaky timeouts are expected. Reason: WebRTC inherently depends on timeouts 06:58:02 INFO - 143 INFO TEST-UNEXPECTED-FAIL | dom/media/tests/mochitest/test_getUserMedia_stopVideoStreamWithFollowupVideo.html | Unexpected callback with = 'ended event never fired' at: ["@http://mochi.test:8888/tests/dom/media/tests/mochitest/test_getUserMedia_stopVideoStreamWithFollowupVideo.html:44:1",""] - expected PASS 06:58:02 INFO - 144 INFO TEST-OK | dom/media/tests/mochitest/test_getUserMedia_stopVideoStreamWithFollowupVideo.html | took 31009ms
Flags: needinfo?(pehrsons)
I haven't managed to reproduce this yet on linux64 Mulet, though I have seen it in fairly recent try runs.
Flags: needinfo?(pehrsons)
Rank: 35
Flags: firefox-backlog+
Priority: -- → P3
backlog: --- → webRTC+
Flags: firefox-backlog+
Inactive; closing (see bug 1180138).
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.