haskell / haskell/cabal

`cabal test` and `cabal benchmark` reportedly don't work for wasm output

Open
#10,923 3 comments 0 reactions 0 assignees View on GitHub
needs triage type: bug
Dominant language
Haskell
Stars
1.7k
Forks
750
Avg merge
4d 3h
Merged PRs (30d)
28

Description

**Describe the bug**
I have heard reports that `cabal test` doesn't work with wasm cross-compilers because it expects to be able to run an executable directly, but you need to use a wasm runner such as `wasmtime` to run them. This is expected to also fail with `cabal benchmark` for the same reason.

**To Reproduce**
I don't have a reproducer; this is from a discussion on the FP Discord.

**Expected behavior**
`cabal test` should be able to run a wasm binary.

**Additional context**
I suspect that support for wasm output (and possibly JS) will require specifying a runner to use. This may also be useful for cross-compilers in general, where the runner would use a provisioned qemu or send the binary to an embedded processor (Raspberry Pi, RISC-V, etc.).

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.