-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[wasmparser] 0.218.0 test suite fails with use of undeclared crate or module
wat`
#1947
Comments
Can you provide steps to reproduce this? Are you perhaps trying to test the crate directly from crates.io? If so that is alas not supported in the Rust ecosystem, so I wouldn't recommend that level of testing. |
The failure is reproducible using the GNU Guix cargo-build-system tooling, which exposes just what is needed for the build. Notably, there is no 'wat' crate being made available. This crate appears to come from the top level of the project and not explicitly referenced as a development dependency in the Cargo.toml file of wasmparser, so we were not providing it. Perhaps it should be? I can't reproduce from a git checkout because then cargo seems to look-up crates in the project top-level and finds a definition for 'wat'. If you'd like to reproduce using the Guix tooling, I can provide simple instructions to do so. |
Building from a wasm-tools git checkout, we can see that
|
Yes!
The growing Rust package collections in GNU Guix begs to differ :-). Like PyPI, not all source distributions contain the required test data files, but in general they do, or don't need any and the test suite just works. Building from the git checkout also works, but I've found that because the source lacks |
Ah ok, sorry but this is not a support way of testing these crates right now. If that doesn't integrate with guix I'm sorry about that but for now you'll basically have to not expect this to work. |
I'm trying to run the test suite, and I'm getting:
The text was updated successfully, but these errors were encountered: