This is a tracking issue for issues surrounding the use of the new wasip1 GOOS target on the [wasmer](https://wasmer.io/) Wasm runtime. We currently do not have a wasmer runner, but manual testing against the wasmer runtime has already yielded some results, namely, it is known that it exhibits a problem similar to wasmtime when it comes to opening directories (see https://github.com/golang/go/issues/59583#issuecomment-1529157141). This issue should not be considered done until we have a working wasmer runner and all tests are either passing or we have documented the failures which we cannot reasonably fix. Currently known failing tests: | Package | Test name | Error | Test log | Fixed | |--------|--------|--------|--------|--------| | archive/tar | TestReader | open testdata/gnu.tar: Bad file number | [Full log](https://storage.googleapis.com/go-build-log/bb3fcca6/wasip1-wasm-wasmer_2d3d63ea.log) | |
Metadata
Metadata
Assignees
Labels
Relationships
Development
Issue actions