Closed Bug 1888067 Opened 1 year ago Closed 1 year ago

[wpt-sync] Sync PR 45357 - peerconnection: Fire data channel events synchronously

Categories

(Core :: WebRTC, task, P4)

task

Tracking

()

RESOLVED FIXED
126 Branch
Tracking Status
firefox126 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(Blocks 2 open bugs, )

Details

(Whiteboard: [wptsync downstream])

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

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

Florent Castelli <orphis@chromium.org> wrote:

peerconnection: Fire data channel events synchronously

When message events are dispatched asynchronously, it is possible to
receive some of those after the state change events are dispatched.
This causes some messages to disappear when a data channel is closing.

Tests are added to verify that all messages sent are received properly
by the remote side as mandated by the specification.

Bug: chromium:40072842
Change-Id: I196cd5b6cae4ea443369b2d9bc98dad474162b23

Reviewed-on: https://chromium-review.googlesource.com/5397720
WPT-Export-Revision: a1130a786b14d3c92d6fd6bf9d14537dec682eba

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 6 subtests

Status Summary

Firefox

OK : 1
CRASH : 1
FAIL : 3[GitHub] 6[Gecko-linux1804-64-qr-debug, Gecko-windows11-64-2009-qr-debug]
TIMEOUT: 1[Gecko-linux1804-64-qr-opt, Gecko-windows11-64-2009-qr-opt] 2[GitHub]
NOTRUN : 2

Chrome

OK : 1
FAIL : 6

Safari

TIMEOUT: 2
NOTRUN : 5

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

Crashes

  • /webrtc/RTCDataChannel-send-close.html [wpt.fyi]: CRASH [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-windows11-32-2009-qr-debug, Gecko-windows11-32-2009-qr-opt], OK [Gecko-linux1804-64-qr-debug, Gecko-windows11-64-2009-qr-debug], TIMEOUT [Gecko-linux1804-64-qr-opt, Gecko-windows11-64-2009-qr-opt, GitHub]

New Tests That Don't Pass

  • /webrtc/RTCDataChannel-send-close.html [wpt.fyi]: CRASH [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-windows11-32-2009-qr-debug, Gecko-windows11-32-2009-qr-opt], OK [Gecko-linux1804-64-qr-debug, Gecko-windows11-64-2009-qr-debug], TIMEOUT [Gecko-linux1804-64-qr-opt, Gecko-windows11-64-2009-qr-opt, GitHub] (Chrome: OK, Safari: TIMEOUT)
    • Datachannel should be able to send and receive all string messages on close: FAIL (Chrome: FAIL, Safari: TIMEOUT)
    • Datachannel should be able to send and receive all arraybuffer messages on close: FAIL (Chrome: FAIL, Safari: NOTRUN)
    • Datachannel should be able to send and receive all blob messages on close: FAIL (Chrome: FAIL, Safari: NOTRUN)
    • Negotiated datachannel should be able to send and receive all string messages on close: FAIL [Gecko-linux1804-64-qr-debug, Gecko-windows11-64-2009-qr-debug], TIMEOUT [GitHub] (Chrome: FAIL, Safari: NOTRUN)
    • Negotiated datachannel should be able to send and receive all arraybuffer messages on close: FAIL [Gecko-linux1804-64-qr-debug, Gecko-windows11-64-2009-qr-debug], NOTRUN [GitHub] (Chrome: FAIL, Safari: NOTRUN)
    • Negotiated datachannel should be able to send and receive all blob messages on close: FAIL [Gecko-linux1804-64-qr-debug, Gecko-windows11-64-2009-qr-debug], NOTRUN [GitHub] (Chrome: FAIL, Safari: NOTRUN)
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/e0f4d38ff371 [wpt PR 45357] - peerconnection: Fire data channel events synchronously, a=testonly https://hg.mozilla.org/integration/autoland/rev/2111da1f7d60 [wpt PR 45357] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 126 Branch
You need to log in before you can comment on or make changes to this bug.