-
Notifications
You must be signed in to change notification settings - Fork 7
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
[CI] Build on JS and WASM backends #84
Conversation
Rename `ci.yml` to `ci.yaml`
Thanks!
What's failing in tests?
Caching would be nice. Yes, presumably you can copy it from the main build job, just adjust cache key. |
On the JS backend, the tests fail to run due to |
Could you please try
? Flipping other flags of |
Use `haskell-actions/setup` instead of `haskell/actions/setup`
Now the testsuite compiles successfully, but there's a linker error:
See https://github.com/konsumlamm/bitvec/actions/runs/7053126518/job/19199568767 for the log. |
@TerrorJack any ideas about @konsumlamm does disabling threaded runtime help? We can make |
Still a linker error:
|
the |
Ok, now linking works, but running fails:
|
4d00ddc
to
c97b53f
Compare
Add `.vscode` to `.gitignore`
c97b53f
to
5080716
Compare
I suppose we have to run tests manually, via |
028e75b
to
65fe3cd
Compare
Now the tests finally run (and pass) under WASM. |
Awesome, many thanks! |
Running the tests doesn't work currently, but building the library does. I took the build steps from https://www.haskell.org/ghcup/guide/#cross-support. Should the actions also cache stuff? If so, could one just copy the caching from the
build
job?Also rename
ci.yml
toci.yaml
(.yaml
is the recommended extension).