Stream: git-wasmtime

Topic: wasmtime / issue #5657 Wasmtime: build release artifacts ...

Wasmtime GitHub notifications bot (Jan 30 2023 at 23:34):

martindevans commented on issue #5657:

Do you know roughly when this will make it into a release?

Wasmtime GitHub notifications bot (Jan 30 2023 at 23:36):

alexcrichton commented on issue #5657:

Our release process is documented here and this'll get released with 6.0.0 on February 20

Wasmtime GitHub notifications bot (Jan 30 2023 at 23:45):

alexcrichton commented on issue #5657:

@cfallin it looks like this failed on main, which can track since the "Build" CI isn't run on PRs any more. Would you be up for investigating that?

Wasmtime GitHub notifications bot (Jan 30 2023 at 23:46):

alexcrichton commented on issue #5657:

Ah nevermind looks like it was failing before this too, I'll try to dig in later

Wasmtime GitHub notifications bot (Jan 30 2023 at 23:50):

cfallin commented on issue #5657:

I had verified it builds locally, so at least the --features all-arch is harmless, I think. As a random guess/hunch, "permission denied" copying the build result may be because the Dockerized CentOS build container writes files as root? Perhaps something updated or changed recently related to that?

Wasmtime GitHub notifications bot (Jan 31 2023 at 04:58):

alexcrichton commented on issue #5657:

Oh @martindevans I forgot about this but you can also test out the artifacts from the dev tag while a release hasn't been made yet.

Wasmtime GitHub notifications bot (Jan 31 2023 at 14:44):

martindevans commented on issue #5657:

The wasmtime.exe from the linked tag works for me :+1:

I didn't test the equivalent binaries on any other platforms though.

Last updated: Dec 23 2024 at 12:05 UTC