alexcrichton opened issue #13880:
Today in particular, but historically as well, there have been a lot of failures in the wasmtime-wasi-nn crate. Some sample logs are:
https://github.com/bytecodealliance/wasmtime/actions/runs/29358428549/job/87172005655
https://github.com/bytecodealliance/wasmtime/actions/runs/29350702096/job/87145948188
https://github.com/bytecodealliance/wasmtime/actions/runs/29340495721/job/87110767184@jlb6740 and @rahulchaphalkar as the defacto-owners of wasmtime-wasi-nn would y'all be able to take a look at this? If this continue to be onerous we'll probably need to disable the tests as it can hold up landing PRs.
alexcrichton added the ci label to Issue #13880.
alexcrichton commented on issue #13880:
alexcrichton commented on issue #13880:
alexcrichton commented on issue #13880:
rahulchaphalkar commented on issue #13880:
Thanks Alex for bringing this to our attention. I'm addressing some of these issues in https://github.com/bytecodealliance/wasmtime/pull/13886 (still a draft). Trying to repro
illegal instructionerror which seems to be on windows.
alexcrichton commented on issue #13880:
Thanks for looking into this! I'm going to keep logging things here so there's a set of logs to draw from if needed as a heads up:
alexcrichton commented on issue #13880:
alexcrichton commented on issue #13880:
alexcrichton commented on issue #13880:
alexcrichton commented on issue #13880:
alexcrichton commented on issue #13880:
@rahulchaphalkar this is a failure after your openvino update landed
rahulchaphalkar commented on issue #13880:
Bummer. Thanks for letting me know. I have opened a bug in onednn https://github.com/uxlfoundation/oneDNN/issues/5689 , and will keep track of it. I don't have the exact Xeon family of platform available to repro it reliably for now, I will keep this issue updated.
Last updated: Jul 29 2026 at 05:03 UTC