-
Notifications
You must be signed in to change notification settings - Fork 265
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
Use forked Wasmtime 14.0.4 with backported fixes #2076
Conversation
2acc1f8
to
3331f65
Compare
Signed-off-by: Lann Martin <lann.martin@fermyon.com>
e2e-tests failure reproduces locally and is confusing:
|
Where are you getting those error logs from? From reading over the error here I think it will require the final commit of #2037 which fixes some guest SDK behavior w.r.t reads/writes |
Sounds like an old version of |
Oh strange; I reran just the one failing test locally and got the above error, but if I run the whole suite there are lots of errors so probably unrelated. |
Signed-off-by: Alex Crichton <alex@alexcrichton.com>
3331f65
to
d824565
Compare
I've been switching between 1.5.1 and 2.0.0 a lot locally; possibly a bad dep cache. |
This fork of wasmtime 14.0.4 includes backports of upstream fixes:
bytecodealliance/wasmtime#7426
bytecodealliance/wasmtime#7475