Closed
Bug 1461496
Opened 7 years ago
Closed 7 years ago
[wpt-sync] Sync PR 10997 - Add test to verify a particular PeerConnection setup does not deadlock
Categories
(Core :: WebRTC, enhancement, P4)
Core
WebRTC
Tracking
()
RESOLVED
FIXED
mozilla62
Tracking | Status | |
---|---|---|
firefox62 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 10997 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/w3c/web-platform-tests/pull/10997
Details from upstream follow.
Kristoffer Erlandsson <kerl@google.com> wrote:
> Add test to verify a particular PeerConnection setup does not deadlock
>
> Does the connection setup in a specific sequence that historically
> triggered a deadlock (https://crbug.com/736725). The test simply
> verifies this specific sequence completes without errors or timeout.
>
> Verified it fails on the deadlock by running the test on the parent commit
> (2485344d4e8792bc4f9716deadda41fbc0d89ad9) of the original bug fix.
>
> BUG=chromium:840737
>
> Change-Id: I93d9d8cb50cad9629268971520de489450d8649b
>
> Reviewed-on: https://chromium-review.googlesource.com/1057249
> WPT-Export-Revision: ea46f5166337cbe0b48fb65f1803fb1a0319985d
Assignee | ||
Updated•7 years ago
|
Component: web-platform-tests → WebRTC
Product: Testing → Core
Assignee | ||
Comment 1•7 years ago
|
||
Assignee | ||
Comment 2•7 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=bd3c8c5a5dc8eb9c4451f65acc5b0765d9726ffc
Assignee | ||
Comment 3•7 years ago
|
||
Ran 1 tests and 1 subtests
OK : 1
PASS : 1
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/4a5ab590207d
[wpt PR 10997] - Add test to verify a particular PeerConnection setup does not deadlock, a=testonly
Comment 5•7 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox62:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla62
You need to log in
before you can comment on or make changes to this bug.
Description
•