Closed Bug 1513231 Opened 10 months ago Closed 9 months ago
wasm spec jit-tests failing on (some) ARM hardware
Forked from bug 1454918. Wasm jit-tests failing on Moto G5: TEST-UNEXPECTED-FAIL | tests/jit-test/jit-test/tests/wasm/spec/float_memory.wast.js | #1 module successfully instantiated: PASS. (code 3, args "") [0.3 s] TEST-UNEXPECTED-FAIL | tests/jit-test/jit-test/tests/wasm/spec/memory_redundancy.wast.js | #1 module successfully instantiated: PASS. (code 3, args "") [0.2 s]
Specifically see bug 1454918 comment 11 for link to failing run.
Should we fix this ARM64 wasm issue before pushing ARM64 Fennec Nightly builds to users? Tentatively tagging as [arm64:m1].
Note this IIUC this is an ARM-32 issue, not an ARM-64 issue. It should be fixed, but likely it's been in the wild for many months already. I would not make it a blocker, but I do want to investigate further.
Thanks for the clarification.
Hardware: ARM64 → ARM
Note that I had to disable several wasm tests to green up the jittests. These included both arm7 and arm64. See <https://hg.mozilla.org/mozilla-central/rev/4688c503e2ee> jit-test/tests/wasm/atomic.js arm64 jit-test/tests/wasm/baseline-abs-addr-opt.js arm64 jit-test/tests/wasm/bce.js arm64 jit-test/tests/wasm/memory.js arm64 jit-test/tests/wasm/spec/float_memory.wast.js arm7 jit-test/tests/wasm/spec/memory_redundancy.wast.js arm7
Bob, do you have a link to a failed test run? I'm curious why the four non-/spec/ tests failed on arm64, did they time out or were there other kinds of failures? (Note we should not track those here because this bug is exclusively about ARM-32 but we might as well have the discussion here.)
I backed out those skips and did a full try run with rebuild 20 which was definitely overkill but guaranteed to get everything: <https://treeherder.mozilla.org/#/jobs?repo=try&revision=879e771626c04bace4d2c0a57e957ae6d1efa38b>. Looks like all "out of memory": <https://taskcluster-artifacts.net/AmQku0U-QymQOVSq7ETc7A/0/public/logs/live_backing.log> baseline-abs-addr-opt.js, memory.js expect a RuntimeError but the others have uncaught out of memory exceptions.
Thanks! We need to track down why those tests OOM. They shouldn't. Tracking this as bug 1517412.
Status: NEW → RESOLVED
Closed: 9 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.