Open Bug 1971998 Opened 7 days ago Updated 18 hours ago

[wpt-sync] Sync PR 53113 - Rudimentary testing that reciever getParameters does header extensions

Categories

(Core :: WebRTC, task, P4)

task

Tracking

()

People

(Reporter: wpt-sync, Unassigned)

References

(Depends on 1 open bug, )

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 53113 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/53113
Details from upstream follow.

Harald Alvestrand <hta@chromium.org> wrote:

Rudimentary testing that reciever getParameters does header extensions

Bug: chromium:423460792
Change-Id: I2ed0e27a455b07d8e674f567bc2d069927311e7c
Reviewed-on: https://chromium-review.googlesource.com/6641542
WPT-Export-Revision: 69a7f708233165a1cf4080ec72fc0e4fcf4fc201

Component: web-platform-tests → WebRTC
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]

CI Results

Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 1 tests and 4 subtests

Status Summary

Firefox

OK : 1
FAIL: 4

Chrome

OK : 1
PASS: 3
FAIL: 1

Safari

OK : 1
PASS: 3
FAIL: 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

Firefox-only Failures

New Tests That Don't Pass

  • /webrtc/RTCRtpReceiver-getParameters.html [wpt.fyi]
    • getParameters() with audio receiver: FAIL (Chrome: PASS, Safari: PASS)
    • getParameters() with video receiver: FAIL (Chrome: PASS, Safari: PASS)
    • getParameters() with simulcast video receiver: FAIL (Chrome: FAIL, Safari: FAIL)
    • getParameters() surfaces codecs on two-way receiver at the right time: FAIL (Chrome: PASS, Safari: PASS)
You need to log in before you can comment on or make changes to this bug.