-
Notifications
You must be signed in to change notification settings - Fork 22
Bump wasmtime
to version 32
#457
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
Conversation
wasmtime-environ = "=31.0.0" | ||
deterministic-wasi-ctx = "=0.1.34" | ||
wasmtime-environ = "=32.0.0" | ||
deterministic-wasi-ctx = { version = "=1.2.0", features = ["wasi-common"] } |
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.
Until #448 is merged.
@@ -18,7 +18,7 @@ module Wasmtime | |||
it "includes the backtrace" do | |||
expect(trap.wasm_backtrace_message).to eq(<<~MSG.rstrip) | |||
error while executing at wasm backtrace: | |||
0: 0x1a - <unknown>!<wasm function 0> | |||
0: 0x1a - <unknown>!<wasm function 0> |
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.
The formatting here changed a bit, I wasn't able to pinpoint if this is intentional in upstream wasmtime though.
Ugh, I think the failures are related to linking. |
Changes so far look good to me. But interested in seeing what the fix for not being able to find |
The issues in rb-sys were fixed upstream (thanks Jeff!), so the Windows issues are now fixed. There's one Valgrind issue that is currently under investigation, so I'm proposing that we merge on red, and follow-up with a fix after the fact. |
New versions of `rustix` don't use libc by default. bytecodealliance/rustix#1389
Memcheck issue was fixed in 20fb455 |
No description provided.