Closed
Bug 1543272
Opened 5 years ago
Closed 5 years ago
[wpt-sync] Sync PR 16165 - Revise tests for datachannel ID handling
Categories
(Core :: WebRTC, defect, P4)
Core
WebRTC
Tracking
()
RESOLVED
FIXED
mozilla69
Tracking | Status | |
---|---|---|
firefox69 | --- | fixed |
People
(Reporter: mozilla.org, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 16165 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/16165
Details from upstream follow.
Harald Alvestrand <hta@chromium.org> wrote:
Revise tests for datachannel ID handling
The tests were not correctly checking for use of preallocated ID.
Bug: chromium:945274
Change-Id: I9bc27ca1ce094f1c2fa5a7d693e1a5e18c3077aa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1546099
Commit-Queue: Harald Alvestrand \<hta@chromium.org>
Reviewed-by: Henrik Boström \<hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#646232}
Assignee | ||
Updated•5 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Assignee | ||
Updated•5 years ago
|
Component: web-platform-tests → WebRTC
Product: Testing → Core
Assignee | ||
Updated•5 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Assignee | ||
Comment 1•5 years ago
|
||
Pushed to try https://treeherder.mozilla.org/#/jobs?repo=try&revision=ab7fdba82142b61dac98af3336e693d6599b4240
Assignee | ||
Comment 2•5 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=a3928a95fe0242f19a5d946d6a06067930c77875
Assignee | ||
Comment 3•5 years ago
|
||
Failed to get results from try push
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/e0dd3b9b76db [wpt PR 16165] - Revise tests for datachannel ID handling, a=testonly
Comment 5•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox69:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
You need to log in
before you can comment on or make changes to this bug.
Description
•