Closed Bug 1858249 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 42466 - Reactivate and fix tests for WebRTC answer state errors

Categories

(Core :: WebRTC, task, P4)

task

Tracking

()

RESOLVED FIXED
121 Branch
Tracking Status
firefox121 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Harald Alvestrand <hta@chromium.org> wrote:

Reactivate and fix tests for WebRTC answer state errors

Bug: chromium:1490510
Change-Id: I7e8553ea9b81d73a5ec9c4f72bf782dee9c69ffb
Reviewed-on: https://chromium-review.googlesource.com/4928688
WPT-Export-Revision: 8eb5055103165e6c2d57c711d842c9f70a1c2881

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

CI Results

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

Total 1 tests and 7 subtests

Status Summary

Firefox

OK : 1
PASS: 5
FAIL: 2

Chrome

OK : 1
PASS: 5
FAIL: 2

Safari

OK : 1
PASS: 6
FAIL: 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

  • /webrtc/RTCPeerConnection-setLocalDescription-answer.html [wpt.fyi]
    • Calling setLocalDescription(answer) from stable state should reject with InvalidStateError: FAIL (Chrome: FAIL, Safari: PASS)
    • Calling setLocalDescription(answer) from have-local-offer state should reject with InvalidStateError: FAIL (Chrome: FAIL, Safari: PASS)
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/83feb71179c2 [wpt PR 42466] - Reactivate and fix tests for WebRTC answer state errors, a=testonly https://hg.mozilla.org/integration/autoland/rev/e087be7bc5a7 [wpt PR 42466] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 121 Branch
You need to log in before you can comment on or make changes to this bug.