testing/deno: Find out why test_ffi fails on aarch64
Follow up for !48979 (comment 323013)
Running tests/integration_tests.rs (target/release/deps/integration_tests-f4e1b7da22424d77)
running 4 tests
test basic ... FAILED
test symbol_types ... ok
test thread_safe_callback ... ok
test event_loop_integration ... ok
failures:
---- basic stdout ----
stdout something
[1, 2, 3, 4, 5, 6, 7, 8]
[4, 5, 6]
[1, 2, 3, 4, 5, 6, 7, 8] [9, 10]
[1, 2, 3, 4, 5, 6, 7, 8]
[ 1, 2, 3, 4, 5, 6 ]
[ 4, 5, 6 ]
[ 4, 5, 6 ]
Hello from pointer!
pointer!
false
true
false
true
false
stderr error: Uncaught AssertionError: isNullBuffer(new Uint8Array()) !== false
throw new AssertionError(message);
^
at assertEquals (file:///builds/alpine/aports/testing/deno/src/deno/test_util/std/testing/asserts.ts:190:9)
at file:///builds/alpine/aports/testing/deno/src/deno/test_ffi/tests/test.js:373:1
ExitStatus(unix_wait_status(256))
thread 'basic' panicked at 'assertion failed: output.status.success()', test_ffi/tests/integration_tests.rs:45:3
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
failures:
basic
test result: FAILED. 3 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 4.11s
It’s from test_ffi/tests/test.js:373:
// V8 bug: inline Uint8Array creation to fast call sees non-null pointer
// https://bugs.chromium.org/p/v8/issues/detail?id=13489
assertEquals(isNullBuffer(new Uint8Array()), false, "isNullBuffer(new Uint8Array()) !== false");
To move forward, I’ve allowed test_ffi
to fail on aarch64 in testing/deno/APKBUILD:236-242.