[arm64] Tests fail with `wasmtime` and `wasmer` runtime on linux-arm64 about ngx_wasm_module

[losfair]

Ran the test with V8. Looks like V8 is currently the most correct engine on AArch64:

Test Summary Report
-------------------
t/03-proxy_wasm/130-proxy_dispatch_http_call.t        (Wstat: 0 Tests: 121 Failed: 5)
  Failed tests:  1-4, 121
  Parse errors: Bad plan.  You planned 120 tests but ran 121.
Files=39, Tests=1633, 101 wallclock secs ( 0.23 usr  0.09 sys +  9.72 cusr  5.06 csys = 15.10 CPU)
Result: FAIL

(this failure seems to be caused by my devbox not having IPv6 - which is expected)

[thibaultcha]

Let's investigate then. I suggest running the tests with verbose mode (https://metacpan.org/pod/Test::Nginx::Socket#TEST_NGINX_VERBOSE), and investigating potential core dumps.

[thibaultcha]

Also I am unsure of the current state of support for M1 & arm64 in wasmtime/wasmer.

[losfair]

This failure on wasmtime:

#   Failed test 't/02-http/001-wasm_call_directive.t TEST 11: wasm_call directive - catch runtime error sanity - status code ok'
#   at /home/zhy/Code/ngx_wasm_module/work/downloads/cpanm/lib/perl5/Test/Nginx/Socket.pm line 940.
#          got: ''
#     expected: '500'

seems to be caused by a missing trap on unsigned integer division. AArch64 native udiv instruction does not trap, so cranelift needs to handle that.

(module
    (func (export "div0")
        i32.const 0
        i32.const 0
        i32.div_u
        drop)
)

[losfair]

connect_timeout isn't working EDIT: not caused by timeout handling - looks like the worker crashed during entry into the http response callback.

#   Failed test 'ERROR: client socket timed out - t/03-proxy_wasm/131-proxy_http_dispatch_timeouts.t TEST 1: proxy_wasm - dispatch_http_call() connection timeout
# '
#   at /home/zhy/Code/ngx_wasm_module/work/downloads/cpanm/lib/perl5/Test/Nginx/Socket.pm line 2210.
!!! resp: [] at /home/zhy/Code/ngx_wasm_module/work/downloads/cpanm/lib/perl5/Test/Nginx/Socket.pm line 743.
parse response

#   Failed test 't/03-proxy_wasm/131-proxy_http_dispatch_timeouts.t TEST 1: proxy_wasm - dispatch_http_call() connection timeout - status code ok'
#   at /home/zhy/Code/ngx_wasm_module/work/downloads/cpanm/lib/perl5/Test/Nginx/Socket.pm line 940.
#          got: ''
#     expected: '500'

#   Failed test 't/03-proxy_wasm/131-proxy_http_dispatch_timeouts.t TEST 1: proxy_wasm - dispatch_http_call() connection timeout - response_body_like - response is expected ()'
#   at /home/zhy/Code/ngx_wasm_module/work/downloads/cpanm/lib/perl5/Test/Nginx/Socket.pm line 1710.
#                   ''
#     doesn't match '(?^s:500 Internal Server Error)'
Testing stap...

#   Failed test 't/03-proxy_wasm/131-proxy_http_dispatch_timeouts.t TEST 1: proxy_wasm - dispatch_http_call() connection timeout - pattern "(?^:\[error\] .*? \[wasm\] dispatch failed \(tcp socket - timed out connecting to \".*?"\))" should match a line in error.log (req 0)'
#   at /home/zhy/Code/ngx_wasm_module/work/downloads/cpanm/lib/perl5/Test/Nginx/Socket.pm line 1288.

[hishamhm]

As a heads-up: I haven't tested V8 support (coming soon via #85) on anything non-x86, but I have made V8_PLATFORM into an environment variable to pick the build target that will be honored by make setup. It uses V8's platform nomenclature, so that means x64 for x86_64 (the default), or arm64 for arm64.

I haven't tested it though, so there might be additional hurdles (see https://v8.dev/docs/compile-arm64 and https://blog.sqreen.com/how-we-built-v8-natively-on-arm/) — if you find any extra tweaks needed to support WasmX with V8 on arm64, those would be welcome additions to util/runtimes/v8.sh!