Is there a quick test case to verify a wasm runtime support range of WASI undefined functions?

[lum1n0us]

There are two list of undefined functions in wasi-libc

• one for wasm-wasi
• one for wasm-wasi-thread

IMO, a Wasm runtime announces to fully support WASI/WASI-thread should be able to provide all host implementations about `__imported_wasi_snapshot_preview1_XXX. Either via runtime itself(like WAMR) or via third-party(like uvwasi or cargo-wasi)

It would be able to verify the combability of variant versions WASI if there is a test. I understand the ultimate goal of was-testsuite is to verify that. But for now, Is there a quick check only about the range?

[loganek]

Hi @lum1n0us , you're right, the goal is to verify:

1. completeness
2. correctness

of WASI implementation in the runtime. At the moment there's no way (at least in wasi-testsuite) to just verify if the function is supported (either correctly or incorrectly) by the runtime; once we have a full coverage, you should be able to to do that, but we still miss a number of functions in test suite.

I'd keep this issue open so as part of this ticket we can implement a set of a sanity checks that hopefully satisfy your requirement short term. Feel free to contribute your tests to this repository too.