Closed Bug 1835095 Opened 1 years ago Closed 1 year ago

[wpt-sync] Sync PR 40229 - webrtc wpt: fix RTP header extension munging

Categories

(Core :: WebRTC, task, P4)

Product:
Core
Component:
WebRTC
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
116 Branch
Tracking Flags:
Tracking Status
firefox116 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Philipp Hancke <phancke@microsoft.com> wrote:

webrtc wpt: fix RTP header extension munging

to unblock
https://webrtc-review.googlesource.com/c/src/+/306223
which throws in RTCRtpSynchronizationSource-senderCaptureTimeOffset.html
due to incorrect munging.

BUG=webrtc:14782

Change-Id: I62995b52cf4e093ec291eaeea135a8e594086e48
Reviewed-on: https://chromium-review.googlesource.com/4567864
WPT-Export-Revision: 3745eaa92827083ee5a7e4c41d4a7a8a5a4d3955

Component: web-platform-tests → WebRTC
Product: Testing → Core

CI Results

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

Total 2 tests and 7 subtests

Status Summary

Firefox

OK : 2
PASS : 8
FAIL : 6

Chrome

OK : 2
PASS : 14

Safari

TIMEOUT: 4
NOTRUN : 12

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

  • /webrtc-extensions/RTCRtpSynchronizationSource-captureTimestamp.html [wpt.fyi]: OK [GitHub], SKIP [Gecko-android-em-7.0-x86_64-lite-qr-opt-geckoview, Gecko-android-em-7.0-x86_64-qr-debug-geckoview, Gecko-android-em-7.0-x86_64-qr-opt-geckoview, Gecko-linux1804-64-qr-debug, Gecko-linux1804-64-qr-opt] (Chrome: OK, Safari: TIMEOUT)
    • [audio] getSynchronizationSources() should contain captureTimestamp if absolute capture time RTP header extension is negotiated: FAIL (Chrome: PASS, Safari: NOTRUN)
    • [video] getSynchronizationSources() should contain captureTimestamp if absolute capture time RTP header extension is negotiated: FAIL (Chrome: PASS, Safari: NOTRUN)
    • Audio and video RTCRtpSynchronizationSource.captureTimestamp are comparable: FAIL (Chrome: PASS, Safari: NOTRUN)
  • /webrtc-extensions/RTCRtpSynchronizationSource-senderCaptureTimeOffset.html [wpt.fyi]: OK [GitHub], SKIP [Gecko-android-em-7.0-x86_64-lite-qr-opt-geckoview, Gecko-android-em-7.0-x86_64-qr-debug-geckoview, Gecko-android-em-7.0-x86_64-qr-opt-geckoview, Gecko-linux1804-64-qr-debug, Gecko-linux1804-64-qr-opt] (Chrome: OK, Safari: TIMEOUT)
    • [audio] getSynchronizationSources() should contain senderCaptureTimeOffset if absolute capture time RTP header extension is negotiated: FAIL (Chrome: PASS, Safari: NOTRUN)
    • [video] getSynchronizationSources() should contain senderCaptureTimeOffset if absolute capture time RTP header extension is negotiated: FAIL (Chrome: PASS, Safari: NOTRUN)
    • Audio and video RTCRtpSynchronizationSource.senderCaptureTimeOffset must be zero: FAIL (Chrome: PASS, Safari: NOTRUN)

Tests Disabled in Gecko Infrastructure

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6869cf6dc7bb [wpt PR 40229] - webrtc wpt: fix RTP header extension munging, a=testonly

https://hg.mozilla.org/mozilla-central/rev/6869cf6dc7bb

Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox116: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 116 Branch
You need to log in before you can comment on or make changes to this bug.