WebAssembly / WebAssembly/wabt
test failures on aarm64
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 8.1k
- Forks
- 827
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 18
Description
-
test/regress/wasm2c-ehv3-setjmp-volatile.txt
expected error code 0, got 250.
STDERR MISMATCH:
--- expected
+++ actual
@@ -0,0 +1 @@
+sigaltstack failed: Invalid argument -
test/wasm2c/spec/exception-handling/throw.txt
expected error code 0, got 250.
STDERR MISMATCH:
--- expected
+++ actual
@@ -0,0 +1 @@
+sigaltstack failed: Invalid argument
[+1864|-2|%100] (103.63s) test/wasm2c/spec/simd_const.txt
**** FAILED ******************************************************************
- test/regress/wasm2c-ehv3-setjmp-volatile.txt
/usr/local/bin/python3 /wabt/test/run-spec-wasm2c.py out/test/regress/wasm2c-ehv3-setjmp-volatile.txt --bindir=/wabt/bin --no-error-cmdline -o out/test/regress/wasm2c-ehv3-setjmp-volatile --enable-exceptions - test/wasm2c/spec/exception-handling/throw.txt
/usr/local/bin/python3 /wabt/test/run-spec-wasm2c.py out/test/wasm2c/spec/exception-handling/throw.wast --bindir=/wabt/bin --no-error-cmdline -o out/test/wasm2c/spec/exception-handling/throw --enable-exceptions
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the two listed cases, test/regress/wasm2c-ehv3-setjmp-volatile.txt and test/wasm2c/spec/exception-handling/throw.txt, with test/run-spec-wasm2c.py on aarm64. Compare the expected and actual stderr, especially the sigaltstack failure; done means these cases pass without the reported error-code or stderr mismatches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python, wasm
- Domain
- operating-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100