test/wasm2c/spec/skip-stack-guard-page.txt fails on 32-bit ARM

I'm getting this test failure when running 1.0.13 test suite on ARM:

- test/wasm2c/spec/skip-stack-guard-page.txt
  expected error code 0, got 1.
  STDERR MISMATCH:
  --- expected
  +++ actual
  @@ -0,0 +1,14 @@
  +Traceback (most recent call last):
  +  File "/builddir/build/BUILD/wabt-1.0.13/test/run-spec-wasm2c.py", line 421, in <module>
  +    sys.exit(main(sys.argv[1:]))
  +  File "/builddir/build/BUILD/wabt-1.0.13/test/run-spec-wasm2c.py", line 413, in main
  +    utils.Executable(os.path.join(out_dir, main_exe),
  +  File "/builddir/build/BUILD/wabt-1.0.13/test/utils.py", line 104, in RunWithArgs
  +    raise error
  +utils.Error: Signal raised running "out/test/wasm2c/spec/skip-stack-guard-page/skip-stack-guard-page": SIGSEGV
  +b''
  +During handling of the above exception, another exception occurred:
  +Traceback (most recent call last):
  +  File "/builddir/build/BUILD/wabt-1.0.13/test/run-spec-wasm2c.py", line 427, in <module>
  +    sys.stderr.write(u'{0}\n'.format(e).encode('ascii', 'replace'))
  +TypeError: write() argument must be str, not bytes
  STDOUT MISMATCH:
  --- expected
  +++ actual
  @@ -1 +0,0 @@
  -10/10 tests passed.

Any idea what's going on here?

Start by reproducing test/wasm2c/spec/skip-stack-guard-page.txt on 32-bit ARM and inspect the failure through test/run-spec-wasm2c.py and test/utils.py. Check both the SIGSEGV from the generated executable and the Python traceback shown in the report. Done means the test completes with exit code 0 and reports 10/10 tests passed without stderr mismatch.