Closed Bug 1536925 Opened 5 years ago Closed 5 years ago

windows/aarch64 - TEST-UNEXPECTED-TIMEOUT | /webrtc/RTCPeerConnection-setRemoteDescription-tracks.https.html | multiple issues

Categories

(Core :: WebRTC, defect, P5)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1538725

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

#[markdown(off)]
Filed by: egao [at] mozilla.com

https://treeherder.mozilla.org/logviewer.html#?job_id=234924560&repo=try

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

Test: wpt10

Platform: windows10-aarch64

Context:
05:59:47 INFO - TEST-PASS | /webrtc/RTCPeerConnection-setRemoteDescription-tracks.https.html | ontrack fires before setRemoteDescription resolves.
05:59:47 INFO - TEST-PASS | /webrtc/RTCPeerConnection-setRemoteDescription-tracks.https.html | addTrack() with two tracks and one stream makes ontrack fire twice with the tracks and shared stream.
05:59:47 INFO - TEST-PASS | /webrtc/RTCPeerConnection-setRemoteDescription-tracks.https.html | addTrack() for an existing stream makes stream.onaddtrack fire.
05:59:47 INFO - TEST-PASS | /webrtc/RTCPeerConnection-setRemoteDescription-tracks.https.html | stream.onaddtrack fires before setRemoteDescription resolves.
05:59:47 INFO - TEST-PASS | /webrtc/RTCPeerConnection-setRemoteDescription-tracks.https.html | addTrack() with a track and two streams makes ontrack fire with a track and two streams.
05:59:47 INFO - TEST-PASS | /webrtc/RTCPeerConnection-setRemoteDescription-tracks.https.html | ontrack's receiver matches getReceivers().
05:59:47 INFO - TEST-PASS | /webrtc/RTCPeerConnection-setRemoteDescription-tracks.https.html | removeTrack() does not remove the receiver.
05:59:47 INFO - TEST-PASS | /webrtc/RTCPeerConnection-setRemoteDescription-tracks.https.html | removeTrack() makes stream.onremovetrack fire and the track to be removed from the stream.
05:59:47 INFO - TEST-PASS | /webrtc/RTCPeerConnection-setRemoteDescription-tracks.https.html | stream.onremovetrack fires before setRemoteDescription resolves.
05:59:47 INFO - TEST-PASS | /webrtc/RTCPeerConnection-setRemoteDescription-tracks.https.html | removeTrack() makes track.onmute fire and the track to be muted.
05:59:47 INFO - TEST-UNEXPECTED-TIMEOUT | /webrtc/RTCPeerConnection-setRemoteDescription-tracks.https.html | track.onmute fires before setRemoteDescription resolves. - Test timed out
05:59:47 INFO -
05:59:47 INFO - TEST-UNEXPECTED-NOTRUN | /webrtc/RTCPeerConnection-setRemoteDescription-tracks.https.html | removeTrack() twice is safe. - expected PASS
05:59:47 INFO - TEST-UNEXPECTED-TIMEOUT | /webrtc/RTCPeerConnection-setRemoteDescription-tracks.https.html | expected OK
05:59:47 INFO - TEST-INFO took 10560ms
05:59:47 INFO - PID 2120 | (ice/NOTICE) ICE(PC:1553061586130000 (id=32212254724 url=https://web-platform.test:8443/webrtc/RTCPeerConnection-setRemoteDescription-tracks.https.): peer (PC:1553061586130000 (id=32212254724 url=https://web-platform.test:8443/webrtc/RTCPeerConnection-setRemoteDescription-tracks.https.:default) no streams with pre-answer requests
05:59:47 INFO - PID 2120 | (ice/NOTICE) ICE(PC:1553061586130000 (id=32212254724 url=https://web-platform.test:8443/webrtc/RTCPeerConnection-setRemoteDescription-tracks.https.): peer (PC:1553061586130000 (id=32212254724 url=https://web-platform.test:8443/webrtc/RTCPeerConnection-setRemoteDescription-tracks.https.:default) no checks to start
05:59:47 INFO - PID 2120 | [Child 7912: Socket Thread]: D/mtransport Couldn't start peer checks on PC:1553061586130000 (id=32212254724 url=https://web-platform.test:8443/webrtc/RTCPeerConnection-setRemoteDescription-tracks.https., assuming trickle ICE
05:59:47 INFO - PID 2120 | (generic/EMERG) Exit UDP socket connected
05:59:47 INFO - PID 2120 | (generic/ERR) UDP socket error:Internal error at z:/build/build/src/dom/network/UDPSocketParent.cpp:269 this=00000287B5205800
05:59:47 INFO - PID 2120 | (ice/WARNING) z:/build/build/src/media/mtransport/third_party/nICEr/src/net/nr_socket_multi_tcp.c:617 function nr_socket_multi_tcp_listen failed with error 3

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.