Closed Bug 1757020 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 32970 - Disable MediaStreamTrackinWorker in tests

Categories

(Core :: Audio/Video: MediaStreamGraph, task, P4)

task

Tracking

()

RESOLVED FIXED
100 Branch
Tracking Status
firefox100 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Tony Herre <toprice@chromium.org> wrote:

Disable MediaStreamTrackinWorker in tests

Our focus is currently on transferability of MediaStreamTracks between
Windows, rather than to workers, and having this enabled in tests is
causing some worrying sounding security bugs from fuzzers.

To be enabled again once we're ready to restart impl in the Worker
scope.

Bug: 1288839,1290586,1291472
Change-Id: I7f735e913c406bdea3ba50e3c7af23b457eb21dd
Reviewed-on: https://chromium-review.googlesource.com/3488386
WPT-Export-Revision: ff7d9c35c026bab8290fa77eb0f808c23589a8c9

PR 32970 applied with additional changes from upstream: 8f3bbf6a457c58a210f987d3ec596b4a56423d3b
Component: web-platform-tests → Audio/Video: MediaStreamGraph
Product: Testing → Core

CI Results

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

Total 1 tests and 1 subtests

Status Summary

Firefox

OK : 1
FAIL: 1

Chrome

OK : 1
FAIL: 1

Safari

OK : 1
FAIL: 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/mediacapture-streams/MediaStreamTrack-transfer.https.html
MediaStreamTrack transfer to Worker: FAIL (Chrome: FAIL, Safari: FAIL)

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d4a429cd8b3f
[wpt PR 32970] - Disable MediaStreamTrackinWorker in tests, a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 100 Branch
You need to log in before you can comment on or make changes to this bug.