1282313 - Intermittent dom/media/tests/mochitest/test_peerConnection_addAudioTrackToExistingVideoStream.html | application timed out after 330 seconds with no output

Status: RESOLVED INCOMPLETE

(Core :: WebRTC, defect, P2)

Description

[Treeherder Bug Filer]

Filed by: [e-mail]

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

http://archive.mozilla.org/pub/mobile/nightly/2016/06/2016-06-26-03-02-13-mozilla-central-android-api-15/mozilla-central_ubuntu64_vm_armv7_large_test-mochitest-media-2-bm117-tests1-linux64-build3.txt.gz

Comment 1

[Andreas Pehrson [:pehrsons]]

Not sure what's going on here. Proper timestamps would have been sweet.

Test seems to have finished as it should:
> 10:39:51     INFO -  807 INFO Run step 95: PC_CHECK_REMOTE_AUDIO_FLOW
> 10:39:51     INFO -  808 INFO Comparing maxima; input[511] = 0, output[511] = 0
> 10:39:51     INFO -  809 INFO Comparing maxima; input[511] = 0, output[511] = 0
> 10:39:51     INFO -  810 INFO Comparing maxima; input[511] = 0, output[23] = 179
> 10:39:51     INFO -  811 INFO Comparing maxima; input[511] = 0, output[23] = 128
> 10:39:51     INFO -  812 INFO Comparing maxima; input[511] = 0, output[23] = 77
> 10:39:51     INFO -  813 INFO Comparing maxima; input[23] = 234, output[23] = 26
> 10:39:51     INFO -  814 INFO TEST-PASS | dom/media/tests/mochitest/test_peerConnection_addAudioTrackToExistingVideoStream.html | input and output audio data matches
> 10:39:51     INFO -  815 INFO TEST-FAIL | dom/media/tests/mochitest/test_peerConnection_addAudioTrackToExistingVideoStream.html | The author of the test has indicated that flaky timeouts are expected.  Reason: WebRTC inherently depends on timeouts
> 10:39:51     INFO -  816 INFO Closing peer connections
> 10:39:51     INFO -  817 INFO TEST-PASS | dom/media/tests/mochitest/test_peerConnection_addAudioTrackToExistingVideoStream.html | iceConnectionState should not be undefined
> 10:39:51     INFO -  818 INFO PeerConnectionWrapper (pcLocal): oniceconnectionstatechange fired, new state is: closed
> 10:39:51     INFO -  819 INFO TEST-PASS | dom/media/tests/mochitest/test_peerConnection_addAudioTrackToExistingVideoStream.html | PeerConnectionWrapper (pcLocal): legal ICE state transition from connected to closed
> 10:39:51     INFO -  820 INFO PeerConnectionWrapper (pcLocal): "onsignalingstatechange" event fired
> 10:39:51     INFO -  821 INFO TEST-PASS | dom/media/tests/mochitest/test_peerConnection_addAudioTrackToExistingVideoStream.html | signalingState is closed
> 10:39:51     INFO -  822 INFO TEST-PASS | dom/media/tests/mochitest/test_peerConnection_addAudioTrackToExistingVideoStream.html | PeerConnectionWrapper (pcLocal): legal signaling state transition from stable to closed
> 10:39:51     INFO -  823 INFO PeerConnectionWrapper (pcLocal): Closed connection.
> 10:39:51     INFO -  824 INFO TEST-PASS | dom/media/tests/mochitest/test_peerConnection_addAudioTrackToExistingVideoStream.html | iceConnectionState should not be undefined
> 10:39:51     INFO -  825 INFO PeerConnectionWrapper (pcRemote): oniceconnectionstatechange fired, new state is: closed
> 10:39:51     INFO -  826 INFO TEST-PASS | dom/media/tests/mochitest/test_peerConnection_addAudioTrackToExistingVideoStream.html | PeerConnectionWrapper (pcRemote): legal ICE state transition from connected to closed
> 10:39:51     INFO -  827 INFO PeerConnectionWrapper (pcRemote): "onsignalingstatechange" event fired
> 10:39:51     INFO -  828 INFO TEST-PASS | dom/media/tests/mochitest/test_peerConnection_addAudioTrackToExistingVideoStream.html | signalingState is closed
> 10:39:51     INFO -  829 INFO TEST-PASS | dom/media/tests/mochitest/test_peerConnection_addAudioTrackToExistingVideoStream.html | PeerConnectionWrapper (pcRemote): legal signaling state transition from stable to closed
> 10:39:51     INFO -  830 INFO PeerConnectionWrapper (pcRemote): Closed connection.
> 10:39:51     INFO -  SUITE-END | took 966s

We just can't detect it?

Comment 2

[Byron Campen [:bwc]]

Looks like a deadlock to me involving ProcessThreadImpl::lock_ and ViEChannelManager::channel_id_critsect_, see thread 12 frames 3 and 1, and thread 63 frames 8 and 2.

Comment 3

[Andreas Pehrson [:pehrsons]]

Sounds bad. Let's bump this a bit then.

Comment 4

[Intermittent Failures Robot]

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

Repository breakdown:
* mozilla-esr52: 1

Platform breakdown:
* linux64: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1282313&startday=2017-10-02&endday=2017-10-08&tree=all

Comment 5

[Cosmin Sabou [:CosminS]]

Reopened because of this fail:

https://treeherder.mozilla.org/#/jobs?repo=autoland&selectedJob=150723085&filter-searchStr=003c7abc6eca552c9c9a1790ad56f144e73d6dc0

Comment 6

[Intermittent Failures Robot]

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

Repository breakdown:
* autoland: 3
* mozilla-inbound: 1

Platform breakdown:
* linux32: 2
* linux64-qr: 1
* linux64: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1282313&startday=2017-12-04&endday=2017-12-10&tree=all

Comment 7

[Intermittent Failures Robot]

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

Repository breakdown:
* try: 1
* autoland: 1

Platform breakdown:
* linux64-qr: 1
* linux32: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1282313&startday=2017-12-11&endday=2017-12-17&tree=all

Comment 8

[Firefox Bug Husbandry Bot]

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

Comment 9

[Intermittent Failures Robot]

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

Repository breakdown:
* mozilla-release: 1

Platform breakdown:
* linux32: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1282313&startday=2018-09-17&endday=2018-09-23&tree=all