Closed
Bug 1409151
Opened 7 years ago
Closed 6 years ago
Intermittent dom/media/tests/mochitest/test_peerConnection_restartIceNoBundle.html | Error in test execution: Error: Timeout checking for stats for track {998721ae-810e-4f06-a73b-e03c4d8f6acc} after at least30000ms waitForRtpFlow@http://mochi.test:8888/te
Categories
(Core :: WebRTC, defect, P5)
Core
WebRTC
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: intermittent-bug-filer, Unassigned)
Details
(Keywords: intermittent-failure)
Comment hidden (Intermittent Failures Robot) |
Comment 2•7 years ago
|
||
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
Updated•7 years ago
|
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Comment hidden (Intermittent Failures Robot) |
Comment 4•7 years ago
|
||
Status: REOPENED → RESOLVED
Closed: 7 years ago → 7 years ago
Resolution: --- → INCOMPLETE
Comment 5•7 years ago
|
||
Recent failure log: https://treeherder.mozilla.org/logviewer.html#?job_id=165355527&repo=autoland&lineNumber=35479
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Comment hidden (Intermittent Failures Robot) |
Comment 7•7 years ago
|
||
Status: REOPENED → RESOLVED
Closed: 7 years ago → 7 years ago
Resolution: --- → INCOMPLETE
Comment 8•7 years ago
|
||
Recent failure log: https://treeherder.mozilla.org/logviewer.html#?job_id=196390358&repo=autoland&lineNumber=72269
09:35:09 INFO - TEST-FAIL | dom/media/tests/mochitest/test_peerConnection_restartIceNoBundle.html | The author of the test has indicated that flaky timeouts are expected. Reason: WebRTC inherently depends on timeouts
09:35:09 INFO - Checking for stats in {"outbound_rtcp_video_0":{"id":"outbound_rtcp_video_0","timestamp":2085938,"type":"inboundrtp","isRemote":true,"kind":"video","mediaType":"video","remoteId":"outbound_rtp_video_0","ssrc":3658480717,"bytesReceived":0,"jitter":0,"packetsLost":0,"packetsReceived":0},"outbound_rtp_video_0":{"id":"outbound_rtp_video_0","timestamp":1535535308457,"type":"outboundrtp","bitrateMean":0,"bitrateStdDev":0,"firCount":0,"framerateMean":0,"framerateStdDev":0,"isRemote":false,"kind":"video","mediaType":"video","nackCount":0,"pliCount":0,"remoteId":"outbound_rtcp_video_0","ssrc":3658480717,"bytesSent":0,"droppedFrames":0,"framesEncoded":0,"packetsSent":0}} for video track {062b052d-cd7a-4b0e-bc13-ec99d39ecab5}, retry number 60
09:35:09 INFO - Should have RTP stats for track {062b052d-cd7a-4b0e-bc13-ec99d39ecab5}
09:35:09 INFO - RTP stats: {"id":"outbound_rtp_video_0","timestamp":1535535308457,"type":"outbound-rtp","bitrateMean":0,"bitrateStdDev":0,"firCount":0,"framerateMean":0,"framerateStdDev":0,"isRemote":false,"kind":"video","mediaType":"video","nackCount":0,"pliCount":0,"remoteId":"outbound_rtcp_video_0","ssrc":3658480717,"bytesSent":0,"droppedFrames":0,"framesEncoded":0,"packetsSent":0}
09:35:09 INFO - Track {062b052d-cd7a-4b0e-bc13-ec99d39ecab5} has 0 outbound-rtp RTP packets.
09:35:09 INFO - TEST-FAIL | dom/media/tests/mochitest/test_peerConnection_restartIceNoBundle.html | The author of the test has indicated that flaky timeouts are expected. Reason: WebRTC inherently depends on timeouts
09:35:09 INFO - Buffered messages finished
09:35:09 INFO - TEST-UNEXPECTED-FAIL | dom/media/tests/mochitest/test_peerConnection_restartIceNoBundle.html | Error in test execution: Error: Timeout checking for stats for track {9cf2e347-9228-4030-b563-c813399d1d8e} after at least30000ms waitForRtpFlow@http://mochi.test:8888/tests/dom/media/tests/mochitest/pc.js:1556:11 ... async*waitForMediaFlow/<@http://mochi.test:8888/tests/dom/media/tests/mochitest/pc.js:1608:58 ... waitForMediaFlow@http://mochi.test:8888/tests/dom/media/tests/mochitest/pc.js:1608:45 ... 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:849:31 ...
09:35:09 INFO - execute/<@dom/media/tests/mochitest/head.js:853:14
09:35:09 INFO - promise callback*execute@dom/media/tests/mochitest/head.js:852:8
09:35:09 INFO - PeerConnectionTest.prototype.run@dom/media/tests/mochitest/pc.js:486:10
09:35:09 INFO - @dom/media/tests/mochitest/test_peerConnection_restartIceNoBundle.html:37:5
09:35:09 INFO - runNetworkTest/<@dom/media/tests/mochitest/pc.js:2213:13
09:35:09 INFO - async*runTestWhenReady/<@dom/media/tests/mochitest/head.js:470:41
09:35:09 INFO - promise callback*runTestWhenReady@dom/media/tests/mochitest/head.js:470:10
09:35:09 INFO - runNetworkTest@dom/media/tests/mochitest/pc.js:2195:9
09:35:09 INFO - async*@dom/media/tests/mochitest/test_peerConnection_restartIceNoBundle.html:15:3
09:35:09 INFO - TEST-FAIL | dom/media/tests/mochitest/test_peerConnection_restartIceNoBundle.html | The author of the test has indicated that flaky timeouts are expected. Reason: WebRTC inherently depends on timeouts
09:35:09 INFO - Closing peer connections
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment 11•6 years ago
|
||
Status: REOPENED → RESOLVED
Closed: 7 years ago → 6 years ago
Resolution: --- → INCOMPLETE
Comment hidden (Intermittent Failures Robot) |
You need to log in
before you can comment on or make changes to this bug.
Description
•