Build/test wasm32-wasip2 in CI #649
Merged
+45
−6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a follow-up from mlua-rs/lua-src-rs#13 which verifies/tests that mlua/lua all work when compiled for a WASI target. While this doesn't have formal documentation yet it also codifies in CI configuration how to build for WASI and get tests passing (notably C compiler configuration and some misc Rust flags).
This moves some
dev-dependencies
that don't compile forwasm32-wasip2
to a different section of the manifest. This additionally annotates panicking tests with#[cfg(not(panic = "abort"))]
to skip those tests on WASI.This does not test either the
send
orasync
feature at this time. Testingsend
requires threads which WASI does not yet support, and testingasync
requires more support in Tokio which is not currently there yet.Closes #366