CI check for wasm isn't working #861

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.

Sign up for GitHub

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

Jump to bottom

Closed

tomaka opened this issue Aug 21, 2020 · 1 comment · Fixed by #863

tomaka commented Aug 21, 2020

Building async-std for the wasm target is completely broken at the moment:

The reason why it hasn't been detected is that the CI of async-std for wasm isn't working. Here's an example.

tomaka changed the title ~~CI for wasm isn't working~~ CI check for wasm isn't working

0x8f701 mentioned this issue

failed to resolve futures_timer #843

Closed

Contributor

jbr commented Aug 23, 2020 •

edited

Loading

#864 addresses this

dignifiedquire mentioned this issue

fix wasm and nostd builds #863

Merged

dignifiedquire closed this as completed in #863

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment