1477710 - Intermittent dom/media/tests/mochitest/test_dataChannel_basicAudioVideo.html | ended never fired for track {4fb76881-ecb0-45a2-abea-9c6b3e90eaf2}

Status: RESOLVED INCOMPLETE

(Core :: WebRTC: Signaling, defect, P5)

Description

[Treeherder Bug Filer]

Filed by: csabou [at] mozilla.com

https://treeherder.mozilla.org/logviewer.html#?job_id=189516476&repo=autoland

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

12:45:02     INFO -  1092 INFO TEST-FAIL | dom/media/tests/mochitest/test_dataChannel_basicAudioVideo.html | The author of the test has indicated that flaky timeouts are expected.  Reason: WebRTC inherently depends on timeouts
12:45:02     INFO -  Buffered messages finished
12:45:02    ERROR -  1093 INFO TEST-UNEXPECTED-FAIL | dom/media/tests/mochitest/test_dataChannel_basicAudioVideo.html | ended never fired for track {4fb76881-ecb0-45a2-abea-9c6b3e90eaf2}
12:45:02     INFO -      closeIt/promise</<@dom/media/tests/mochitest/pc.js:155:25
12:45:02     INFO -      promise callback*closeIt/promise<@dom/media/tests/mochitest/pc.js:150:18
12:45:02     INFO -      closeIt@dom/media/tests/mochitest/pc.js:145:19
12:45:02     INFO -      PeerConnectionTest.prototype.closePC@dom/media/tests/mochitest/pc.js:164:5
12:45:02     INFO -      PeerConnectionTest.prototype.close/<@dom/media/tests/mochitest/pc.js:177:17
12:45:02     INFO -      promise callback*PeerConnectionTest.prototype.close@dom/media/tests/mochitest/pc.js:174:10
12:45:02     INFO -      PeerConnectionTest.prototype.run/<@dom/media/tests/mochitest/pc.js:486:17
12:45:02     INFO -      promise callback*PeerConnectionTest.prototype.run@dom/media/tests/mochitest/pc.js:485:10
12:45:02     INFO -      @dom/media/tests/mochitest/test_dataChannel_basicAudioVideo.html:20:5
12:45:02     INFO -      runNetworkTest/<@dom/media/tests/mochitest/pc.js:2212:13
12:45:02     INFO -      async*runTestWhenReady/<@dom/media/tests/mochitest/head.js:476:41
12:45:02     INFO -      promise callback*runTestWhenReady@dom/media/tests/mochitest/head.js:476:10
12:45:02     INFO -      runNetworkTest@dom/media/tests/mochitest/pc.js:2194:9
12:45:02     INFO -      async*@dom/media/tests/mochitest/test_dataChannel_basicAudioVideo.html:15:3
12:45:02     INFO -  Not taking screenshot here: see the one that was previously logged

Comment 1

[meck93]

Dear Reader,

We are a joint research team from the University of Zurich, Switzerland* and Mozilla** and are building a tool to automatically recognize the type of an intermittent-failure, such as the one here.

By automatically recognizing the type of failure, the tool should provide a starting point for the bug fixing process. To evaluate and improve the tool, we kindly ask your feedback.
    
Tool Result - this intermittent-failure is most likely affected by a:
Concurrency Issue: This includes tests in which failures occur due to thread management issues (different threads or their outcomes depending on an implicit ordering), race conditions and/or deadlocks, and issues related to an asynchronous waits (e.g. a process trying to access an external resource or continuing before the external resource is available).

Feedback: 
1. Did the tool correctly recognize the type of intermittent-failure? (please also explain why or why not)
2. Did the information from the tool help your analysis, the bug fixing process, or anything in the process? (please also let us know how the tool was useful and/or what would improve the tool's usefulness for you)

Thank you very much for your help! 
*Moritz, Fabio and Alberto (http://www.ifi.uzh.ch/en/zest/team.html)
**Marco Castellucio (https://marco-c.github.io/)

Comment 2

[Firefox Bug Husbandry Bot]

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