Wasm testsuite failure: incoherent results between wasmtime/nodejs
When running the testsuite for the wasm backend, using wasmtime/nodejs as different cross emulators, there exist cases that work with one emulator but fails with the other one. This strongly suggests we're encountering implementation-defined behavior in the WASI syscall layer of different engines.
For the time being, we default to wasmtime as our runner, so we're more interested in cases which fail in wasmtime but works in nodejs. There are two cases left that belong to this kind: openFile009
/T4808
. Setting up this tracking ticket so I can revisit the issue later and see what really went wrong in wasmtime.