Repository navigation
Tests fail for target wasm32-wasi #273
Description
Running cargo build --target wasm32-wasi succeeds, but cargo wasi test fails:
- The
pathbuffails since it relies onenv::temp_dir(), which currently panics when running in wasi (see: Support creating temporary files and directories WebAssembly/WASI#306 ) - The
prop_oobandtestable_unit_panictests fails: under wasi, this test panics. When decorating with#[should_panic], they fails under normal (non-wasi) tests
Activity
Spoonbender commentedon Feb 1, 2021
Just to elaborate on the 2nd case:
According to Testing in WASI, "The
wasm32-wasitarget for Rust is effectively apanic=aborttarget which has no support for unwinding". This means that theAssertUnwindSafefunction used in tester.rs can't actually perform its duty for this target (or any otherpanic=aborttarget).Additionally, when running
cargo wasi test, all tests decorated#[should_panic]are ignored.This means we need to decide how we'd like
quickcheckto behave in case of wasi or any other target that doesn't support unwinding.The
std::panic::set_hookfunction might be helpful here, as it allows setting a hook that runs on both unwinding and aborting targets.Adding support for aborting targets, however, could be considered a completely new feature for
quicktest- and for the time being we might just ensure tests pass for wasi w/o adding this support.