-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
wasi-nn: switch testing infrastructure to Rust #6895
Changes from all commits
53cee5a
2420a06
ec7e765
d993154
7879e24
8c3323f
aa85952
e1eb40c
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
This file was deleted.
This file was deleted.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
This example project is similar to | ||
[`image-classification`](../image-classification/) but uses named models. |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
This example project demonstrates using the `wasi-nn` API to perform ML | ||
inference. It consists of Rust code that is built using the `wasm32-wasi` | ||
target. It is used by `wasi-nn`'s tests. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the
test-check
feature here primarily for thereqwest
dependency? If that goes away could this part go away to and unconditionally usecfg(test)
for thetest_check
stuff?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, kind of. I need to be able to use the
test_check
module from various places: unit tests, integration tests, Wasmtime CLI tests... When I was trying to make this work I observed that I could#[cfg(test)]
thetest_check
module and still use it for unit tests but not for the other cases. I actually need this logic available (somehow) in the public interface of the crate. Or perhaps not "the crate" but rather "a crate": I could move this logic to a separate crate likewasmtime-wasi-nn-test
and create adev-dependency
on that?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah ok yeah makes sense, and yes if it's required outside this crate then
#[cfg(test)]
won't work. That being said though since there's no dependencies behind this implementation any more withreqwest
replaced I think it'd be fine to unconditionally include this functionality in the crate and other embedders would largely just ignore it.