test failures on aarm64

[SoothedTau]

• 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

[SoniEx2]

what are you running this on?

[SoothedTau]

Apple M3 Max - Latest MacOS Beta

[SoniEx2]

hmm...

that's strange, we can't see any reason these two tests should be singled out like this.

[shravanrn]

Fwiw, I've occasionally run into this too (mostly when testing segue for wasm2c). I'm not fully sure why this happens at the moment, but iirc, in my case, it happens during cleanup after the test finishes runs correctly.