Remove testing ONNX from CI #10411
Remove testing ONNX from CI #10411
Conversation
This is blocking CI currently as a downloaded artifact is currently offline. This can be re-enabled once that's fixed.
|
cc @abrown |
This is blocking CI currently as a downloaded artifact is currently offline. This can be re-enabled once that's fixed.
* Add release notes for 31.0.0 * Remove testing ONNX from CI (#10411) This is blocking CI currently as a downloaded artifact is currently offline. This can be re-enabled once that's fixed.
PR bytecodealliance#10411 disabled ONNX testing in CI due to failures to download ONNX packages. This change restores that testing in hopes that any HTTP related issues are now resolved.
|
Dear all, Is there any update for re-enabling this test? The reason why I ask above question is that currently, I failed to build the onnx feature through "cargo build --features component-model,wasi-nn,wasmtime-wasi-nn/onnx". It seems that wasmtime with version 32 or 33 are incompatible with neither the latest ort version v2.0.0-rc.10 nor ort version v2.0.0-rc.9. Kind Regards, |
|
Oh this is something we didn't track well and forgot about, but turning it back on is fine to happen at any time! |
|
Hi @alexcrichton, thanks and nice to hear your quick response. I am looking forward to hearing your good news for turning it back on! |
|
Hi @alexcrichton, by the way, since I’d like to test the ONNX feature, it would be great if you could share your schedule (when it is available) for turning it back on. Much appreciated! |
|
Ah as with many things open source there's no strict schedule for things like this. Maintainers are frequently busy and this is free software so for things like this it can often be on you as a user to help out. Which is to say: no schedule, this may not happen unless it's contributed. You're of course welcome to file a PR yourself or file a dedicated issue about this to help track this. |
|
@TrumsZ, can you open a PR to undo what this PR does? I'll help review it. |
This is blocking CI currently as a downloaded artifact is currently offline. This can be re-enabled once that's fixed.