Closed Bug 1592171 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 19966 - Implement ServiceWorkerContainer.onmessageerror.

Categories

(Core :: DOM: Core & HTML, task, P4)

task

Tracking

()

RESOLVED FIXED
mozilla72
Tracking Status
firefox72 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Wei Wang <wei4.wang@intel.com> wrote:

Implement ServiceWorkerContainer.onmessageerror.

Bug:926102
Change-Id: I60e73dcb69de4a2876cc966dfa1809a30510b5f2
Reviewed-on: https://chromium-review.googlesource.com/1864409
WPT-Export-Revision: 42e8ea1eac5289c44e565e3030c5448fd47d575d

Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core

GitHub CI Results

wpt.fyi PR Results Base Results

Ran 2 tests and 2 subtests

Firefox

TIMEOUT: 4

Chrome

OK : 2
FAIL: 2

Safari

OK : 1
FAIL : 1
TIMEOUT: 2

Firefox-only failures

/wasm/serialization/module/window-serviceworker-success.https.html: Firefox: TIMEOUT

Other new tests that's don't pass

/wasm/serialization/module/window-serviceworker-success.https.html
Test ServiceWorkerContainer.onmessageerror using WebAssembly.Module: Firefox: TIMEOUT, Chrome: FAIL, Safari: FAIL

/html/infrastructure/safe-passing-of-structured-data/shared-array-buffers/window-serviceworker-success.https.html: Firefox: TIMEOUT, Chrome: OK, Safari: TIMEOUT
Test ServiceWorkerContainer.onmessageerror using SharedArrayBuffer: Firefox: TIMEOUT, Chrome: FAIL, Safari: TIMEOUT

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/50096a40306b [wpt PR 19966] - Implement ServiceWorkerContainer.onmessageerror., a=testonly https://hg.mozilla.org/integration/autoland/rev/1b755b9b187b [wpt PR 19966] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla72
You need to log in before you can comment on or make changes to this bug.