1551786 - Intermittent Tier 2 TEST-UNEXPECTED-TIMEOUT | /webrtc/RTCDataChannel-bufferedAmount.html | Data channel bufferedamount returns the same amount if no more data is sent on the channel - Test timed out

Status: RESOLVED INCOMPLETE

(Core :: WebRTC, defect, P5)

Description

[Treeherder Bug Filer]

Filed by: rgurzau [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=246499251&repo=mozilla-central
Full log: https://queue.taskcluster.net/v1/task/UlZegkDXQ4efRaonp7QT4g/runs/0/artifacts/public/logs/live_backing.log

---

02:24:46 INFO - PID 3368 | /src/media/mtr[Child 3864: Main Thread]: D/DataChannel Maximum message size (outgoing data): 1073741823 (set=yes, enforced=no)
02:24:46 INFO - ....
02:24:46 INFO - PID 3368 | ansport/third_party/[Child 3864: Main Thread]: D/DataChannel Connect DTLS local 5000, remote 5000
02:24:46 INFO - .
02:24:46 INFO - PID 3368 | nICEr/src/net/nr_socket_multi_tcp.c:617 function nr_socket_multi_tcp_listen failed with error 3
02:24:46 INFO -
02:24:46 INFO - TEST-PASS | /webrtc/RTCDataChannel-bufferedAmount.html | bufferedAmount initial value should be 0 for both peers
02:24:46 INFO - TEST-PASS | /webrtc/RTCDataChannel-bufferedAmount.html | bufferedAmount should increase to byte length of encoded unicode string sent
02:24:46 INFO - TEST-PASS | /webrtc/RTCDataChannel-bufferedAmount.html | bufferedAmount should increase to byte length of buffer sent
02:24:46 INFO - TEST-PASS | /webrtc/RTCDataChannel-bufferedAmount.html | bufferedAmount should increase to size of blob sent
02:24:46 INFO - TEST-PASS | /webrtc/RTCDataChannel-bufferedAmount.html | bufferedAmount should increase by byte length for each message sent
02:24:46 INFO - TEST-PASS | /webrtc/RTCDataChannel-bufferedAmount.html | bufferedAmount should not decrease immediately after initiating closure
02:24:46 INFO - TEST-PASS | /webrtc/RTCDataChannel-bufferedAmount.html | bufferedAmount should not decrease after closing the peer connection
02:24:46 INFO - TEST-PASS | /webrtc/RTCDataChannel-bufferedAmount.html | Data channel bufferedamountlow event fires after send() is complete
02:24:46 INFO - TEST-PASS | /webrtc/RTCDataChannel-bufferedAmount.html | Data channel bufferedamount is data.length on send(data)
02:24:46 INFO - TEST-UNEXPECTED-TIMEOUT | /webrtc/RTCDataChannel-bufferedAmount.html | Data channel bufferedamount returns the same amount if no more data is sent on the channel - Test timed out
02:24:46 INFO -
02:24:46 INFO - TEST-UNEXPECTED-NOTRUN | /webrtc/RTCDataChannel-bufferedAmount.html | Data channel bufferedamountlow event fires only once after multiple consecutive send() calls - expected PASS
02:24:46 INFO -
02:24:46 INFO - TEST-UNEXPECTED-NOTRUN | /webrtc/RTCDataChannel-bufferedAmount.html | Data channel bufferedamountlow event fires after each sent message - expected PASS
02:24:46 INFO - TEST-UNEXPECTED-TIMEOUT | /webrtc/RTCDataChannel-bufferedAmount.html | expected OK
02:24:46 INFO - TEST-INFO took 41096ms

Comment 1

[Intermittent Failures Robot]

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

Repository breakdown:

• mozilla-central: 3

Platform breakdown:

• windows10-aarch64: 3

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1551786&startday=2019-05-13&endday=2019-05-19&tree=all

Comment 2

[Intermittent Failures Robot]

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

Repository breakdown:

• mozilla-central: 2

Platform breakdown:

• windows10-aarch64: 2

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1551786&startday=2019-05-20&endday=2019-05-26&tree=all

Comment 3

[Intermittent Failures Robot]

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

Repository breakdown:

• mozilla-central: 4

Platform breakdown:

• windows10-aarch64: 3
• windows10-64-qr: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1551786&startday=2019-05-27&endday=2019-06-02&tree=all

Comment 4

[Intermittent Failures Robot]

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

Repository breakdown:

• mozilla-central: 1

Platform breakdown:

• windows10-aarch64: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1551786&startday=2019-06-03&endday=2019-06-09&tree=all

Comment 5

[Intermittent Failures Robot]

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

Repository breakdown:

• mozilla-central: 1

Platform breakdown:

• windows10-aarch64: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1551786&startday=2019-06-10&endday=2019-06-16&tree=all

Comment 6

[Intermittent Failures Robot]

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

Repository breakdown:

• mozilla-central: 1

Platform breakdown:

• windows10-aarch64: 1

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

Comment 7

[Firefox Bug Husbandry Bot]

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

Comment 8

[Natalia Csoregi [:nataliaCs]]

https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=259306693&repo=mozilla-beta&lineNumber=23144

Comment 9

[Intermittent Failures Robot]

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

Repository breakdown:

• mozilla-beta: 1

Platform breakdown:

• windows10-64-shippable-qr: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1551786&startday=2019-07-29&endday=2019-08-04&tree=all

Comment 10

[Firefox Bug Husbandry Bot]

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