You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I made some changes to the way wasm builds in CI in #2137, basically making it a standalone target instead of piggybacking on the ubuntu/x86 build, and building directly with cargo instead of using wasm-pack.
While developing that change I noticed that running a cargo test with the wasm target fails:
cargo test --target wasm32-unknown-unknown --no-default-features --all --verbose
In order to keep the project moving I disabled failed tests failing the build, which is clearly not a desirable state to be in. Ideally the warnings and errors produced when running this command would be fixed so we can put the test guardrails back up.
The text was updated successfully, but these errors were encountered:
I made some changes to the way wasm builds in CI in #2137, basically making it a standalone target instead of piggybacking on the ubuntu/x86 build, and building directly with cargo instead of using wasm-pack.
While developing that change I noticed that running a
cargo test
with the wasm target fails:In order to keep the project moving I disabled failed tests failing the build, which is clearly not a desirable state to be in. Ideally the warnings and errors produced when running this command would be fixed so we can put the test guardrails back up.
The text was updated successfully, but these errors were encountered: