Update wasi-testsuite submodule (#11802)* Update wasi-testsuite submoduleBring in some infrastructure for running wasip3 tests. There's a fewcurrent test failures which are flagged here as well.
Update wasi-testsuite submodule (#11802)* Update wasi-testsuite submoduleBring in some infrastructure for running wasip3 tests. There's a fewcurrent test failures which are flagged here as well.prtest:full* Update test ignores* Ignore another test on Windows
show more ...
Update and refactor how wasi-testsuite is run (#11560)* Update and refactor how wasi-testsuite is runThis commit updates the `WebAssembly/wasi-testuite` submodule in thisrepository which hasn't
Update and refactor how wasi-testsuite is run (#11560)* Update and refactor how wasi-testsuite is runThis commit updates the `WebAssembly/wasi-testuite` submodule in thisrepository which hasn't been updated once in the past 2 years. This thenadditionally refactors how tests are run:* A new top-level test is added at `tests/wasi.rs` similar to `tests/wast.rs`.* The top-level test uses `libtest_mimic` to enable running tests in parallel.* Using `libtest_mimic` enables running a test-at-a-time.* Using `libtest_mimic` enables seeing a list of failures instead of just the first failure.* Component versions of tests are run in addition to core wasm versions of tests.* Minor updates are made to the adapter and wasmtime-wasi to get some tests passing.* The list of allowed failures is updated with a `FIXME`-per-test of what's remaining.prtest:full* Fix in-tree tests with new behavior* Add Windows exemptions* Fix tests with wasi-common
Update the wasi_testsuite submodule (#8829)* Update the wasi_testsuite submoduleThis commit updates the wasi_testsuite submodule which we haven'tupdated in a little over a year and applies a few
Update the wasi_testsuite submodule (#8829)* Update the wasi_testsuite submoduleThis commit updates the wasi_testsuite submodule which we haven'tupdated in a little over a year and applies a few small fixes but mostlyignores new tests.* Add another ignore#
test: fix more wasi_testsuite test cases (#6365)Instead of passing environment variables from the spec file to thesandboxed environment, we set them for the execution environment of theprocess (t
test: fix more wasi_testsuite test cases (#6365)Instead of passing environment variables from the spec file to thesandboxed environment, we set them for the execution environment of theprocess (therefore they were not available for WASM test application).
test: add cases from `wasi-testsuite` (#6341)* wasi: add the `wasi-testsuite` tests for wasi-commonAs described [here], this uses the `prod/testsuite-base` branch in whichthe tests are built as
test: add cases from `wasi-testsuite` (#6341)* wasi: add the `wasi-testsuite` tests for wasi-commonAs described [here], this uses the `prod/testsuite-base` branch in whichthe tests are built as `.wasm` files.[here]: https://github.com/WebAssembly/wasi-testsuite/#getting-started* chore: update `walkdir` everywhere to its latest versionThis is done in order to use it for `wasi_testsuite` testing.* vet: extend `walkdir`'s exemption* test: factor out `get_wasmtime_command`This will be helpful for `wasi_testsuite` testing.* test: use all `wasi-testsuite` test casesThis change alters the `wasi_testsuite` test to run all of the availabletest cases in [wasi-testsuite]. This involved making the test runner abit more robust to the various shapes of JSON specifications in thatproject. Unfortunately, the `wasi_testsuite` test fails some of thecases, so I added a `WASI_COMMON_IGNORE_LIST` to avoid thesetemporarily. (This may remind some of the Wasm testsuite ignore lists inCranelift; those relied on `build.rs` to create a `#[test]` for eachtest case, which I felt is not yet needed here).It's unclear to me why the tests are failing. It could be because:- wasi-common has a bug- wasi-testsuite overspecifies (or incorrectly specifies) a test- the test runner incorrectly configures Wasmtime's CLI execution.But this change makes it easier to resolve this. Remove the file from`WASI_COMMON_IGNORE_LIST` and run `cargo test wasi_testsuite ----nocapture`. The printed output will show the expected result, theactual result, and a command to replicate the failure from the commandline.[wasi-testsuite]: https://github.com/WebAssembly/wasi-testsuite* review: add "shrinking" comment
wasi-threads: run test suite (#5907)* wasi-threads: run test suiteThis change enables the running of the wasi-threads [test suite]. Itrelies on a Wasmtime CLI binary being available and runs all
wasi-threads: run test suite (#5907)* wasi-threads: run test suiteThis change enables the running of the wasi-threads [test suite]. Itrelies on a Wasmtime CLI binary being available and runs all `*.wasm`and `*.wat` files present in the test suite directory. The results ofeach execution are compared against a JSON spec file with the same basename as the WebAssembly module. The spec file defines the expected exitcode, e.g.This commit does not yet build any `*.c` or `*.s` files from the testsuite. That could be done later, perhaps upstream; in the meantime, thiswork is still valuable as it lays the foundation for running other WASItests from the in-progress [wasi-testsuite] which share the same JSONspec infrastructure.[test suite]: https://github.com/WebAssembly/wasi-threads/tree/main/test/testsuite[wasi-testsuite]: https://github.com/WebAssembly/wasi-testsuite* review: move testsuite to top-level tests* fix: remove now-unnecessary wasi-threads test* fix: update testsuite submodule name* fix: ignore tests on Windowsprtest:full* fix: `cfg_attr` syntaxprtest:full