Closed Bug 1464817 Opened 7 years ago Closed 7 years ago

Many WebAssembly.Global errors when Gecko 62 becomes late beta

Categories

(Core :: JavaScript Engine: JIT, defect, P1)

defect

Tracking

()

RESOLVED FIXED
mozilla62
Tracking Status
firefox-esr52 --- unaffected
firefox-esr60 --- unaffected
firefox60 --- unaffected
firefox61 --- unaffected
firefox62 + verified

People

(Reporter: ccoroiu, Unassigned)

References

Details

[Tracking Requested - why for this release]: This failure started on today's late beta simulations: https://treeherder.mozilla.org/#/jobs?repo=try&revision=4c7a399c9f4a06be5e3063f6c55252bf7cc13b1a&filter-resultStatus=testfailed&filter-resultStatus=busted&filter-resultStatus=exception&filter-resultStatus=retry&filter-resultStatus=usercancel&filter-resultStatus=runnable&selectedJob=180554434 This is the failure message: TEST-UNEXPECTED-FAIL | tests/jit-test/jit-test/tests/wasm/spec/jsapi.js | /builds/worker/workspace/build/tests/jit-test/jit-test/lib/wasm-testharness.js:31:15 Error: 'WebAssembly.Global' data property: FAIL. (code 3, args "") [0.1 s]
Flags: needinfo?(jseward)
I _believe_ this problem will go away when WebAssembly.Global is enabled by default. This will happen when bug 1464656 lands, which should be within the next few hours. Then we can come back to this and see if it is fixed.
Flags: needinfo?(jseward)
Do we still have this issue now that bug 1464656 landed?
Flags: needinfo?(ccoroiu)
Priority: -- → P1
Tracking in case this reopens.
You need to log in before you can comment on or make changes to this bug.