Adds e2e to test wasmedge shim

[jsturtevant]

The wasmedge shim wasn't being tested and we have a make target that will test it.

[Mossaka]

LGTM!

[Mossaka]

Actually it looks like the gh action has "Startup failure"

[Mossaka]

Could you please fix this error?

The workflow is not valid. .github/workflows/ci.yml (Line: 87, Col: 1): Unexpected value 'e2e-wasmedge'

[jsturtevant]

Could you please fix this error?

The workflow is not valid. .github/workflows/ci.yml (Line: 87, Col: 1): Unexpected value 'e2e-wasmedge'

was missing an indent 🦤

[jsturtevant]

this needs a few of the updates to the makefile that are in #133. Will rebase and update once that is in

[jsturtevant]

looks like k3s didn't set up correctly in the CI:

ctr: failed to dial "/run/k3s/containerd/containerd.sock": connection error: desc = "transport: error while dialing: dial unix /run/k3s/containerd/containerd.sock: connect: connection refused"

[jsturtevant]

I am getting the same error locally:

$ runwasi on  add-wasmedge-job [$] is 📦 v0.1.0 via 🦀 v1.70.0 
> make test/k3s
rustup target add wasm32-wasi
info: component 'rust-std' for target 'wasm32-wasi' is up to date
cd crates/wasi-demo-app && cargo build
.....
ctr: failed to dial "/run/k3s/containerd/containerd.sock": connection error: desc = "transport: error while dialing: dial unix /run/k3s/containerd/containerd.sock: connect: connection refused"
make: *** [Makefile:96: test/k3s] Error 1

@defims any ideas?

[devigned]

@jsturtevant my guess is that the containerd config is malformed in some way and is causing containerd to fail during startup.

[jsturtevant]

Issue was that it took 20-30s for the k8s node to come fully online, it is passing now

[Mossaka]

Shall I merge?

[jsturtevant]

I rebased, added a timeout to the ctr command and removed the vscode settings file. If tests pass I think we are good 👍