When trying to run one of the wasi-fyi tests, namely fs_remove_dir_all, I noticed it always gets compiled, evident by the cranelift log when using RUST_LOG=trace. This happens despite the sha256 checksum of the .wasm file staying the same.
Since I don't see the output of the module, I'm guessing sth goes wrong during compilation and the runtime does not get to actually cache and run it.
This does not happen when using --singlepass or --llvm.
When trying to run one of the wasi-fyi tests, namely
fs_remove_dir_all
, I noticed it always gets compiled, evident by the cranelift log when usingRUST_LOG=trace
. This happens despite the sha256 checksum of the .wasm file staying the same.Since I don't see the output of the module, I'm guessing sth goes wrong during compilation and the runtime does not get to actually cache and run it.
This does not happen when using
--singlepass
or--llvm
.