Closed Bug 1476438 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 12040 - webrtc wpt: rename RTCPeerConnection-addTransceiver.html to .https.html

Categories

(Core :: WebRTC, enhancement, P4)

Product:
Core
Component:
WebRTC
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla63
Tracking Flags:
Tracking Status
firefox63 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream]) 

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

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

Philipp Hancke <philipp.hancke@googlemail.com> wrote:
>  webrtc wpt: rename RTCPeerConnection-addTransceiver.html to .https.html
>  
>  BUG=836871
>  
>  Change-Id: I16e2419717601e3bb89e83df720eee31cc631edc
>  
>  Reviewed-on: https://chromium-review.googlesource.com/1140781
>  WPT-Export-Revision: e35c3f4199d4b257546935dfe30d7fe295eb1087
Component: web-platform-tests → WebRTC
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Ran 1 tests and 15 subtests
OK     : 1
PASS   : 10
FAIL   : 5

New tests that have failures or other problems:
/webrtc/RTCPeerConnection-addTransceiver.https.html
    addTransceiver() with readonly fec set should throw InvalidAccessError: FAIL
    addTransceiver() with readonly rtx set should throw InvalidAccessError: FAIL
    addTransceiver() with readonly ssrc set should throw InvalidAccessError: FAIL
    addTransceiver() with rid containing invalid non-alphanumeric characters should throw TypeError: FAIL
    addTransceiver() with rid longer than 16 characters should throw TypeError: FAIL
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/8f4a236178f9
[wpt PR 12040] - webrtc wpt: rename RTCPeerConnection-addTransceiver.html to .https.html, a=testonly
https://hg.mozilla.org/mozilla-central/rev/8f4a236178f9
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox63: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in before you can comment on or make changes to this bug.