WasmEdge
WasmEdge copied to clipboard
[WASINN] Support PyTorch Backend
Enable pytorch backend in the Wasi-NN plugin.
Codecov Report
:exclamation: No coverage uploaded for pull request base (
proposal/wasi_nn@952e515
). Click here to learn what that means. The diff coverage isn/a
.
@@ Coverage Diff @@
## proposal/wasi_nn #1654 +/- ##
===================================================
Coverage ? 81.41%
===================================================
Files ? 127
Lines ? 18099
Branches ? 3904
===================================================
Hits ? 14736
Misses ? 2407
Partials ? 956
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more
Hi @gusye1234 If you want to test the PyTorch part, you can temporarily remove the other workflow files/jobs. Then add them back once you finish the PyTorch workflow. This can reduce the total workflow execution time and accelerate your iteration. The reason is that our organization only has 20 action runners and we have lots of action jobs. The remaining jobs which may not be related to your testing will execute and take the seats of those runners. And this may make your waiting time an extended period.
Hi @gusye1234 If you want to test the PyTorch part, you can temporarily remove the other workflow files/jobs. Then add them back once you finish the PyTorch workflow. This can reduce the total workflow execution time and accelerate your iteration. The reason is that our organization only has 20 action runners and we have lots of action jobs. The remaining jobs which may not be related to your testing will execute and take the seats of those runners. And this may make your waiting time an extended period.
Thanks for the reminder! And sorry for my debug pushings disturbing you guys a lot...
Is there a way to temporarily configure to remove the other jobs? Or I have to remove them in the .yaml
files?
Just create a temp commit which remove those files or non-related jobs. Once you finish, then revert that commit.