Closed Bug 1727704 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 30191 - insertable streams: expose payload type

Categories

(Testing :: web-platform-tests, task, P4)

Product:
Testing
Component:
web-platform-tests
Type:
task

Tracking

(firefox94 fixed)

Status:
RESOLVED FIXED
Milestone:
94 Branch
Tracking Flags:
Tracking Status
firefox94 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

b'Philipp Hancke <philipp.hancke@googlemail.com>' wrote:

insertable streams: expose payload type

exposes the payload type in the encoded audio/video frame metadata
spec PR:
https://github.com/w3c/webrtc-encoded-transform/pull/117

BUG=webrtc:13077

Change-Id: I17340aec0b18637d7c1f3222add496a8aeb346ae
Reviewed-on: https://chromium-review.googlesource.com/3118568
WPT-Export-Revision: 8c2d2c4d3c93c2f148374035018a98c61dc1cd07

CI Results

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

Total 5 tests and 2 subtests

Status Summary

Firefox

OK : 5
FAIL: 13

Chrome

OK : 5
PASS: 13

Safari

OK : 5
FAIL: 13

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/webrtc-encoded-transform/RTCPeerConnection-insertable-streams-audio.https.html
Frames flow correctly using insertable streams: FAIL (Chrome: PASS, Safari: FAIL)
Frames flow correctly using insertable streams when receiver starts negotiation: FAIL (Chrome: PASS, Safari: FAIL)
RTCRtpSender.createEncodedStream() throws if not requested in PC configuration: FAIL (Chrome: PASS, Safari: FAIL)
RTCRtpReceiver.createEncodedStream() throws if not requested in PC configuration: FAIL (Chrome: PASS, Safari: FAIL)
Enqueuing the same frame twice fails: FAIL (Chrome: PASS, Safari: FAIL)
/webrtc-encoded-transform/RTCPeerConnection-insertable-streams-errors.https.html
RTCRtpSender.createEncodedStream() throws if not requested in PC configuration: FAIL (Chrome: PASS, Safari: FAIL)
RTCRtpReceiver.createEncodedStream() throws if not requested in PC configuration: FAIL (Chrome: PASS, Safari: FAIL)
Enqueuing the same frame twice fails: FAIL (Chrome: PASS, Safari: FAIL)
/webrtc-encoded-transform/RTCPeerConnection-insertable-streams-video-frames.https.html
Key and Delta frames are sent and received: FAIL (Chrome: PASS, Safari: FAIL)
/webrtc-encoded-transform/RTCPeerConnection-insertable-streams-video.https.html
Frames flow correctly using insertable streams: FAIL (Chrome: PASS, Safari: FAIL)
Frames flow correctly using insertable streams when receiver starts negotiation: FAIL (Chrome: PASS, Safari: FAIL)
/webrtc-encoded-transform/RTCPeerConnection-insertable-streams-worker.https.html
RTCRtpSender readable stream transferred to a Worker and the Worker sends an RTCEncodedAudioFrame back: FAIL (Chrome: PASS, Safari: FAIL)
RTCRtpSender readable stream transferred to a Worker and the Worker sends an RTCEncodedVideoFrame back: FAIL (Chrome: PASS, Safari: FAIL)

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2c8d9363e6c8
[wpt PR 30191] - insertable streams: expose payload type, a=testonly

https://hg.mozilla.org/mozilla-central/rev/2c8d9363e6c8

Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox94: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 94 Branch
You need to log in before you can comment on or make changes to this bug.