Run all crates.io tests against wasm target to uncover fresh bugs #38802
Labels
C-tracking-issue
Category: An issue tracking the progress of sth. like the implementation of an RFC
O-wasm
Target: WASM (WebAssembly), http://webassembly.org/
T-infra
Relevant to the infrastructure team, which will review and decide on the PR/issue.
To quickly get an idea for the ecosystem support for wasm we can pretty quickly run all the tests in the world with cargobomb. I think it makes a lot of sense, once some of the other low-hanging fruit is fixed, to run all crates' test suites under wasm before making the final push for production.
The text was updated successfully, but these errors were encountered: