Wasmtime GitHub notifications bot (Mar 17 2025 at 18:36): Wasmtime GitHub notifications bot (Mar 17 2025 at 18:36):alexcrichton requested abrown for a review on PR #10411.
Wasmtime GitHub notifications bot (Mar 17 2025 at 18:36):alexcrichton requested wasmtime-default-reviewers for a review on PR #10411.
Wasmtime GitHub notifications bot (Mar 17 2025 at 18:36):alexcrichton opened PR #10411 from alexcrichton:disable-onnx-testing to bytecodealliance:main:
This is blocking CI currently as a downloaded artifact is currently offline. This can be re-enabled once that's fixed.
<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
Wasmtime GitHub notifications bot (Mar 17 2025 at 18:37):alexcrichton commented on PR #10411:
Failures are:
Wasmtime GitHub notifications bot (Mar 17 2025 at 18:38):alexcrichton commented on PR #10411:
cc @abrown
Wasmtime GitHub notifications bot (Mar 17 2025 at 19:52):fitzgen submitted PR review.
Wasmtime GitHub notifications bot (Mar 17 2025 at 20:15):fitzgen merged PR #10411.
Wasmtime GitHub notifications bot (Jun 16 2025 at 09:05):TrumsZ commented on PR #10411:
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,
Haiqing Zhao
Wasmtime GitHub notifications bot (Jun 16 2025 at 14:24):alexcrichton commented on PR #10411:
Oh this is something we didn't track well and forgot about, but turning it back on is fine to happen at any time!
Wasmtime GitHub notifications bot (Jun 16 2025 at 15:38):TrumsZ commented on PR #10411:
Hi @alexcrichton, thanks and nice to hear your quick response. I am looking forward to hearing your good news for turning it back on!
Wasmtime GitHub notifications bot (Jun 17 2025 at 06:52):TrumsZ commented on PR #10411:
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!
Wasmtime GitHub notifications bot (Jun 17 2025 at 14:30):alexcrichton commented on PR #10411:
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.
Wasmtime GitHub notifications bot (Jun 17 2025 at 22:42):abrown commented on PR #10411:
@TrumsZ, can you open a PR to undo what this PR does? I'll help review it.
Wasmtime GitHub notifications bot (Jun 19 2025 at 01:57):TrumsZ commented on PR #10411:
@abrown Yes, please take a lot for the PR https://github.com/bytecodealliance/wasmtime/pull/11071.
Last updated: Dec 06 2025 at 06:05 UTC