Closed Bug 1676278 Opened 5 years ago Closed 5 years ago

Intermittent [TV] dom/media/webrtc/tests/mochitests/test_peerConnection_stats.html | Error in test execution: Error: Waiting for synced RTCP timed out after at least 20000ms waitForSyncedRtcp@https://example.com/tests/dom/media/webrtc/tests/mochitests/pc.

Categories

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

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Unassigned)

Details

(Keywords: intermittent-failure)

Filed by: nbeleuzu [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=321233019&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/C7Xqnih9TC-GHkX3WWw6uA/runs/0/artifacts/public/logs/live_backing.log
Reftest URL: https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/C7Xqnih9TC-GHkX3WWw6uA/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1


[task 2020-11-09T20:42:06.839Z] 20:42:06     INFO - TEST-FAIL | dom/media/webrtc/tests/mochitests/test_peerConnection_stats.html | The author of the test has indicated that flaky timeouts are expected.  Reason: WebRTC inherently depends on timeouts 
[task 2020-11-09T20:42:06.839Z] 20:42:06     INFO - Buffered messages finished
[task 2020-11-09T20:42:06.839Z] 20:42:06     INFO - TEST-UNEXPECTED-FAIL | dom/media/webrtc/tests/mochitests/test_peerConnection_stats.html | Error in test execution: Error: Waiting for synced RTCP timed out after at least 20000ms waitForSyncedRtcp@https://example.com/tests/dom/media/webrtc/tests/mochitests/pc.js:1934:11 ...  
[task 2020-11-09T20:42:06.839Z] 20:42:06     INFO - SimpleTest.ok@https://example.com/tests/SimpleTest/SimpleTest.js:417:16
[task 2020-11-09T20:42:06.839Z] 20:42:06     INFO - execute/<@https://example.com/tests/dom/media/webrtc/tests/mochitests/head.js:929:11```
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.