Closed Bug 1766490 Opened 2 years ago Closed 2 years ago

Intermittent dom/media/webrtc/tests/mochitests/test_peerConnection_setParameters_maxFramerate.html | fps is an appropriate value (10) for rate (8)

Categories

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

defect

Tracking

()

RESOLVED DUPLICATE of bug 1777079
Tracking Status
firefox-esr91 --- unaffected
firefox99 --- unaffected
firefox100 --- unaffected
firefox101 --- fix-optional
firefox102 --- fix-optional

People

(Reporter: intermittent-bug-filer, Unassigned, NeedInfo)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: intermittent-failure, regression)

Filed by: smolnar [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=375827825&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/CbxlERZvSF2r1tIf6TPdMg/runs/0/artifacts/public/logs/live_backing.log
Reftest URL: https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/CbxlERZvSF2r1tIf6TPdMg/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1


INFO - TEST-PASS | dom/media/webrtc/tests/mochitests/test_peerConnection_setParameters_maxFramerate.html | fps is an appropriate value (13) for rate (15) 
[task 2022-04-26T14:37:25.246Z] 14:37:25     INFO - Run step 53: PC_LOCAL_SET_MAX_FRAMERATE_8
[task 2022-04-26T14:37:25.247Z] 14:37:25     INFO - TEST-FAIL | dom/media/webrtc/tests/mochitests/test_peerConnection_setParameters_maxFramerate.html | The author of the test has indicated that flaky timeouts are expected.  Reason: WebRTC inherently depends on timeouts 
[task 2022-04-26T14:37:25.247Z] 14:37:25     INFO - Buffered messages logged at 14:37:25
[task 2022-04-26T14:37:25.248Z] 14:37:25     INFO - inbound-rtp stats: {"id":"a5671e3e","timestamp":1650983845059,"type":"inbound-rtp","codecId":"767d454c","kind":"video","mediaType":"video","ssrc":794511207,"discardedPackets":0,"jitter":0.0015444444444444444,"packetsDiscarded":0,"packetsLost":0,"packetsReceived":89,"bytesReceived":73479,"firCount":0,"framesDecoded":64,"framesPerSecond":10,"nackCount":0,"pliCount":0,"remoteId":"459411c8"}
[task 2022-04-26T14:37:25.248Z] 14:37:25     INFO - Buffered messages finished
[task 2022-04-26T14:37:25.249Z] 14:37:25     INFO - TEST-UNEXPECTED-FAIL | dom/media/webrtc/tests/mochitests/test_peerConnection_setParameters_maxFramerate.html | fps is an appropriate value (10) for rate (8) 
[task 2022-04-26T14:37:25.249Z] 14:37:25     INFO - SimpleTest.ok@https://example.com/tests/SimpleTest/SimpleTest.js:417:16
[task 2022-04-26T14:37:25.249Z] 14:37:25     INFO - checkMaxFrameRate@https://example.com/tests/dom/media/webrtc/tests/mochitests/test_peerConnection_setParameters_maxFramerate.html:23:5
[task 2022-04-26T14:37:25.249Z] 14:37:25     INFO - Run step 54: PC_LOCAL_SET_MAX_FRAMERATE_1
[task 2022-04-26T14:37:25.250Z] 14:37:25     INFO - TEST-FAIL | dom/media/webrtc/tests/mochitests/test_peerConnection_setParameters_maxFramerate.html | The author of the test has indicated that flaky timeouts are expected.  Reason: WebRTC inherently depends on timeouts 
[task 2022-04-26T14:37:25.250Z] 14:37:25     INFO - GECKO(1530) | [Child 1535: WebrtcWorker #2]: I/signaling [WebrtcWorker #2|WebrtcVideoSessionConduit] VideoStreamFactory.cpp:207: CreateEncoderStreams Input frame 640x480, RID  scaling to 640x480
[task 2022-04-26T14:37:25.251Z] 14:37:25     INFO - GECKO(1530) | [Child 1535: WebrtcWorker #2]: I/signaling [WebrtcWorker #2|WebrtcVideoSessionConduit] VideoStreamFactory.cpp:234: CreateEncoderStreams Stream with RID  maxFps=1 (global max fps = 60)
[task 2022-04-26T14:37:25.854Z] 14:37:25     INFO - GECKO(1530) | (stun/INFO) STUN-CLIENT(consent): Received response; processing
[task 2022-04-26T14:37:25.855Z] 14:37:25     INFO - GECKO(1530) | (ice/INFO) ICE(PC:{584488ad-9127-46cb-a927-64cd6ee59c91} 1650983836442283 (id=8589934597 url=https://example.com/tests/dom/media/webrtc/tests/moc)/STREAM(PC:{584488ad-9127-46cb-a927-64cd6ee59c91} 1650983836442283 (id=8589934597 url=https://example.com/tests/dom/media/webrtc/tests/moc transport-id=transport_0 - 83640adc:845d33147732cb6fd26a37893faa2212)/COMP(1): Consent refreshed
[task 2022-04-26T14:37:27.086Z] 14:37:27     INFO - inbound-rtp stats: {"id":"a5671e3e","timestamp":1650983847084,"type":"inbound-rtp","codecId":"767d454c","kind":"video","mediaType":"video","ssrc":794511207,"discardedPackets":0,"jitter":0.0013777777777777777,"packetsDiscarded":0,"packetsLost":0,"packetsReceived":96,"bytesReceived":80116,"firCount":0,"framesDecoded":67,"framesPerSecond":1,"nackCount":0,"pliCount":0,"remoteId":"459411c8"}
[task 2022-04-26T14:37:27.086Z] 14:37:27     INFO - TEST-PASS | dom/media/webrtc/tests/mochitests/test_peerConnection_setParameters_maxFramerate.html
Summary: Intermittent [TV] dom/media/webrtc/tests/mochitests/test_peerConnection_setParameters_maxFramerate.html | fps is an appropriate value (10) for rate (8) → Intermittent dom/media/webrtc/tests/mochitests/test_peerConnection_setParameters_maxFramerate.html | fps is an appropriate value (10) for rate (8)

Appeared with the landing of Bug 1611957.
:bwc can you take a look?

Flags: needinfo?(docfaraday)
Regressed by: 1611957

Set release status flags based on info from the regressing bug 1611957

Has Regression Range: --- → yes

Seems like the framerate controls in libwebrtc are just a little bit flaky. I suppose I could widen the tolerances, or maybe give it more time to settle at a valid rate. Does not seem to fail very frequently though.

Set release status flags based on info from the regressing bug 1611957

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