Closed
Bug 1454753
Opened 6 years ago
Closed 6 years ago
Intermittent dom/media/tests/mochitest/test_peerConnection_stats.html | Error in test execution: Error: Element _remote_{f9d7aa09-b0be-48ae-8d0a-2e925de9aaf3} should progress currentTime timeout/<@http://mochi.test:8888/tests/dom/media/tests
Categories
(Core :: WebRTC, defect, P5)
Core
WebRTC
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: intermittent-bug-filer, Unassigned)
Details
(Keywords: intermittent-failure)
Filed by: ncsoregi [at] mozilla.com
https://treeherder.mozilla.org/logviewer.html#?job_id=174132547&repo=mozilla-inbound
https://queue.taskcluster.net/v1/task/eNobQZhYQfq-jNVNYN8CTA/runs/0/artifacts/public/logs/live_backing.log
16:38:03 INFO - 1409 INFO TEST-PASS | dom/media/tests/mochitest/test_peerConnection_stats.html | RTP flowing for video track {391f9b00-622d-4b99-b51c-1480f8e9e4c8}
16:38:03 INFO - Buffered messages finished
16:38:03 ERROR - 1410 INFO TEST-UNEXPECTED-FAIL | dom/media/tests/mochitest/test_peerConnection_stats.html | Error in test execution: Error: Element _remote_{f9d7aa09-b0be-48ae-8d0a-2e925de9aaf3} should progress currentTime timeout/<@http://mochi.test:8888/tests/dom/media/tests/mochitest/head.js:595:63 ... promise callback*timeout@http://mochi.test:8888/tests/dom/media/tests/mochitest/head.js:595:26 ... waitForMediaElementFlow@http://mochi.test:8888/tests/dom/media/tests/mochitest/pc.js:1506:28 ... waitForMediaFlow/<@http://mochi.test:8888/tests/dom/media/tests/mochitest/pc.js:1606:22 ... waitForMediaFlow@http://mochi.test:8888/tests/dom/media/tests/mochitest/pc.js:1602:7 ... PC_LOCAL_WAIT_FOR_MEDIA_FLOW@http://mochi.test:8888/tests/dom/media/tests/mochitest/templates.js:374:12 ... execute/</<@http://mochi.test:8888/tests/dom/media/tests/mochitest/head.js:854:31 ... promise callback*execute/<@http://mochi.test:8888/tests/dom/media/tests/mochitest/head.js:852:14 ... execute@http://mochi.test:8888/tests/dom/media/tests/mochitest/head.js:847:12 ... PeerConnectionTest.prototype.run@http://mochi.test:8888/tests/dom/media/tests/mochitest/pc.js:485:10 ... @http://mochi.test:8888/tests/dom/media/tests/mochitest/test_peerConnection_stats.html:551:3 ... runNetworkTest/<@http://mochi.test:8888/tests/dom/media/tests/mochitest/pc.js:2214:13 ... async*runTestWhenReady/<@http://mochi.test:8888/tests/dom/media/tests/mochitest/head.js:475:41 ... promise callback*runTestWhenReady@http://mochi.test:8888/tests/dom/media/tests/mochitest/head.js:475:10 ... runNetworkTest@http://mochi.test:8888/tests/dom/media/tests/mochitest/pc.js:2196:9 ... async*@http://mochi.test:8888/tests/dom/media/tests/mochitest/test_peerConnection_stats.html:540:1 ...
16:38:03 INFO - execute/<@dom/media/tests/mochitest/head.js:858:14
16:38:03 INFO - promise callback*execute@dom/media/tests/mochitest/head.js:847:12
16:38:03 INFO - PeerConnectionTest.prototype.run@dom/media/tests/mochitest/pc.js:485:10
16:38:03 INFO - @dom/media/tests/mochitest/test_peerConnection_stats.html:551:3
16:38:03 INFO - runNetworkTest/<@dom/media/tests/mochitest/pc.js:2214:13
16:38:03 INFO - async*runTestWhenReady/<@dom/media/tests/mochitest/head.js:475:41
16:38:03 INFO - promise callback*runTestWhenReady@dom/media/tests/mochitest/head.js:475:10
16:38:03 INFO - runNetworkTest@dom/media/tests/mochitest/pc.js:2196:9
16:38:03 INFO - async*@dom/media/tests/mochitest/test_peerConnection_stats.html:540:1
16:38:03 INFO - 1411 INFO TEST-FAIL | dom/media/tests/mochitest/test_peerConnection_stats.html | The author of the test has indicated that flaky timeouts are expected. Reason: WebRTC inherently depends on timeouts
16:38:03 INFO - 1412 INFO Closing peer connections
16:38:03 INFO - 1413 INFO Waiting for track {f9d7aa09-b0be-48ae-8d0a-2e925de9aaf3} (audio) to end.
16:38:03 INFO - 1414 INFO TEST-FAIL | dom/media/tests/mochitest/test_peerConnection_stats.html | The author of the test has indicated that flaky timeouts are expected. Reason: WebRTC inherently depends on timeouts
16:38:03 INFO - 1415 INFO Waiting for track {f637bc8e-13e1-4ee7-a79f-865db4f8081e} (video) to end.
16:38:03 INFO - 1416 INFO TEST-FAIL | dom/media/tests/mochitest/test_peerConnection_stats.html | The author of the test has indicated that flaky timeouts are expected. Reason: WebRTC inherently depends on timeouts
Updated•6 years ago
|
Component: Telemetry → WebRTC
Product: Toolkit → Core
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
Comment 4•6 years ago
|
||
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment 7•6 years ago
|
||
Status: REOPENED → RESOLVED
Closed: 6 years ago → 6 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•