Closed
Bug 1760167
Opened 3 years ago
Closed 3 years ago
[wpt-sync] Sync PR 33166 - Test that serializing a `WebAssembly.Memory`-backed buffer works
Categories
(Core :: JavaScript: WebAssembly, task, P4)
Core
JavaScript: WebAssembly
Tracking
()
RESOLVED
FIXED
100 Branch
Tracking | Status | |
---|---|---|
firefox100 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 33166 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/33166
Details from upstream follow.
Andreu Botella <andreu@andreubotella.com> wrote:
Test that serializing a
WebAssembly.Memory
-backed buffer worksThe existing test makes sure that transfering the buffer throws a
TypeError
exception, but V8 currently also throws when serializing it, which should not be the case.
Assignee | ||
Updated•3 years ago
|
Component: web-platform-tests → Javascript: WebAssembly
Product: Testing → Core
Assignee | ||
Comment 1•3 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=29a274c37edb8673fffb805ceda12642a5eebc5e
Assignee | ||
Comment 2•3 years ago
|
||
CI Results
Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 1 tests and 2 subtests
Status Summary
Firefox
OK : 1
PASS: 2
Chrome
OK : 1
FAIL: 2
Safari
OK : 1
PASS: 2
Links
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/407e4d45bb70
[wpt PR 33166] - Test that serializing a `WebAssembly.Memory`-backed buffer works, a=testonly
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/1fc1d63aae8a
[wpt PR 33166] - Test that serializing a `WebAssembly.Memory`-backed buffer works, a=testonly
Comment 5•3 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox100:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 100 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•