1456693 - Intermittent dom/media/tests/mochitest/test_peerConnection_restartIce.html | Error in test execution: Error: Timeout checking for stats for track ... after at least30000ms waitForRtpFlow@http://mochi.test:8888/tests/dom/media/tests/mochitest/pc.js:1555:11

Status: RESOLVED INCOMPLETE

(Core :: WebRTC, defect, P5)

Description

[Treeherder Bug Filer]

Filed by: csabou [at] mozilla.com

https://treeherder.mozilla.org/logviewer.html#?job_id=175426980&repo=mozilla-inbound

https://queue.taskcluster.net/v1/task/DwOHwHuDScydIyu4CcismQ/runs/0/artifacts/public/logs/live_backing.log

23:10:20     INFO -  1809 INFO TEST-FAIL | dom/media/tests/mochitest/test_peerConnection_restartIce.html | The author of the test has indicated that flaky timeouts are expected.  Reason: WebRTC inherently depends on timeouts
23:10:20     INFO -  Buffered messages finished
23:10:20    ERROR -  1810 INFO TEST-UNEXPECTED-FAIL | dom/media/tests/mochitest/test_peerConnection_restartIce.html | Error in test execution: Error: Timeout checking for stats for track {d71d93ad-4eac-4ad9-afb0-85124af4f6a8} after at least30000ms waitForRtpFlow@http://mochi.test:8888/tests/dom/media/tests/mochitest/pc.js:1555:11 ... async*waitForMediaFlow/<@http://mochi.test:8888/tests/dom/media/tests/mochitest/pc.js:1607:58 ... waitForMediaFlow@http://mochi.test:8888/tests/dom/media/tests/mochitest/pc.js:1607: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_restartIce.html:35:5 ... 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_restartIce.html:15:3 ...
23:10:20     INFO -      execute/<@dom/media/tests/mochitest/head.js:858:14
23:10:20     INFO -      promise callback*execute@dom/media/tests/mochitest/head.js:847:12
23:10:20     INFO -      PeerConnectionTest.prototype.run@dom/media/tests/mochitest/pc.js:485:10
23:10:20     INFO -      @dom/media/tests/mochitest/test_peerConnection_restartIce.html:35:5
23:10:20     INFO -      runNetworkTest/<@dom/media/tests/mochitest/pc.js:2214:13
23:10:20     INFO -      async*runTestWhenReady/<@dom/media/tests/mochitest/head.js:475:41
23:10:20     INFO -      promise callback*runTestWhenReady@dom/media/tests/mochitest/head.js:475:10
23:10:20     INFO -      runNetworkTest@dom/media/tests/mochitest/pc.js:2196:9
23:10:20     INFO -      async*@dom/media/tests/mochitest/test_peerConnection_restartIce.html:15:3
23:10:20     INFO -  1811 INFO TEST-FAIL | dom/media/tests/mochitest/test_peerConnection_restartIce.html | The author of the test has indicated that flaky timeouts are expected.  Reason: WebRTC inherently depends on timeouts
23:10:20     INFO -  1812 INFO Closing peer connections

Comment 1

[Intermittent Failures Robot]

1 failures in 780 pushes (0.001 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-inbound: 1

Platform breakdown:
* windows10-64-qr: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1456693&startday=2018-04-23&endday=2018-04-29&tree=trunk

Comment 2

[Intermittent Failures Robot]

2 failures in 551 pushes (0.004 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-inbound: 1
* mozilla-beta: 1

Platform breakdown:
* osx-10-10: 1
* macosx64-nightly: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1456693&startday=2018-04-30&endday=2018-05-06&tree=trunk

Comment 3

[Intermittent Failures Robot]

1 failures in 632 pushes (0.002 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-inbound: 1

Platform breakdown:
* windows10-64-qr: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1456693&startday=2018-05-21&endday=2018-05-27&tree=trunk

Comment 4

[Firefox Bug Husbandry Bot]

https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup