[wpt-sync] Sync PR 32862 - WebKit export of https://bugs.webkit.org/show_bug.cgi?id=236268
Categories
(Core :: JavaScript: WebAssembly, task, P4)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox100 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
(Blocks 1 open bug, )
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 32862 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/32862
Details from upstream follow.
Asumu Takikawa <asumu@igalia.com> wrote:
WebKit export of https://bugs.webkit.org/show_bug.cgi?id=236268
WebKit export from this bug: https://bugs.webkit.org/show_bug.cgi?id=236268
These are new WPT tests for the WebAssembly / ES modules integration proposal (https://github.com/WebAssembly/esm-integration). All marked tentative as the proposal is still in phase 2.
|
Assignee | |
Updated•3 years ago
|
|
||
Comment 1•3 years ago
|
||
Ms2ger, do you know anything about these? There is an increasingly large backlog of wasm wpt-sync items, some quite old, that never seem to be closed. Not suggesting you're responsible, just asking for information.
- James for good measure.
|
|
Assignee | |
Comment 3•3 years ago
|
||
|
||
Comment 4•3 years ago
|
||
The sync is currently behind; we ran into an issue with some upstream changes that broke some tests in a way that wasn't noticed until we tried to land the changes in m-c. I'm working on it.
|
|
Assignee | |
Comment 5•3 years ago
|
||
|
|
Assignee | |
Comment 6•3 years ago
|
||
CI Results
Ran 12 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 13 tests and 1 subtests
Status Summary
Firefox
OK : 8
FAIL : 8
TIMEOUT: 5
NOTRUN : 1
Chrome
OK : 7
FAIL : 7
TIMEOUT: 6
NOTRUN : 2
Safari
OK : 9
FAIL : 9
TIMEOUT: 4
Links
Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base
Details
New Tests That Don't Pass
/wasm/webapi/esm-integration/execute-start.tentative.html
Importing a WebAssembly module should execute the start function.: FAIL (Chrome: FAIL, Safari: FAIL)
/wasm/webapi/esm-integration/exported-names.tentative.html: TIMEOUT (Chrome: TIMEOUT, Safari: TIMEOUT)
/wasm/webapi/esm-integration/invalid-bytecode.tentative.html
Test that imports of invalid WebAssembly modules leads to WebAssembly.CompileError on window.: FAIL (Chrome: FAIL, Safari: FAIL)
/wasm/webapi/esm-integration/js-wasm-cycle-errors.tentative.html
Check cyclic linking between JavaScript and WebAssembly where JavaScript is higher in the module graph.: FAIL (Chrome: FAIL, Safari: FAIL)
/wasm/webapi/esm-integration/js-wasm-cycle.tentative.html: TIMEOUT (Chrome: TIMEOUT, Safari: TIMEOUT)
/wasm/webapi/esm-integration/module-parse-error.tentative.html
Test that imports of invalid WebAssembly modules leads to WebAssembly.CompileError on window.: FAIL (Chrome: FAIL, Safari: FAIL)
/wasm/webapi/esm-integration/resolve-export.tentative.html
Re-export of missing Wasm export should result in SyntaxError.: FAIL (Chrome: FAIL, Safari: FAIL)
/wasm/webapi/esm-integration/wasm-import-wasm-export.tentative.html: TIMEOUT (Chrome: TIMEOUT, Safari: TIMEOUT)
/wasm/webapi/esm-integration/wasm-import.tentative.html
Invalid imports for WebAssembly modules should error.: FAIL (Chrome: FAIL, Safari: FAIL)
/wasm/webapi/esm-integration/wasm-js-cycle.tentative.html: TIMEOUT (Chrome: TIMEOUT, Safari: TIMEOUT)
/wasm/webapi/esm-integration/wasm-to-wasm-link-error.tentative.html
Link errors for imports between WebAssembly modules should be reported.: FAIL (Chrome: FAIL, Safari: FAIL)
/wasm/webapi/esm-integration/worker-import.tentative.html
Testing import of WebAssembly from JavaScript worker: FAIL (Chrome: NOTRUN, Safari: FAIL)
/wasm/webapi/esm-integration/worker.tentative.html: TIMEOUT (Chrome: TIMEOUT, Safari: OK)
Testing WebAssembly worker: NOTRUN (Chrome: NOTRUN, Safari: FAIL)
|
||
Comment 8•3 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/1f4137cef64d
https://hg.mozilla.org/mozilla-central/rev/d465daf1c378
Description
•