Skip to content
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

Emscripten targets broken on CI #1591

Closed
gnzlbg opened this issue Nov 13, 2019 · 0 comments · Fixed by #1697
Closed

Emscripten targets broken on CI #1591

gnzlbg opened this issue Nov 13, 2019 · 0 comments · Fixed by #1697
Labels
A-CI Area: CI-related items

Comments

@gnzlbg
Copy link
Contributor

gnzlbg commented Nov 13, 2019

This tracks re-enabling CI for emscripten targets. This should happen when #1478 is merged.

@gnzlbg gnzlbg added the A-CI Area: CI-related items label Nov 13, 2019
bors added a commit that referenced this issue Feb 10, 2021
Re-enable CI for `asmjs-unknown-emscripten`

#1591 was closed by #1697 but it was only for `wasm32-unknown-emscripten` actually. We should make a new issue and link to it instead if it's still broken.
r? `@ghost`
bors added a commit that referenced this issue Feb 10, 2021
Re-enable CI for `asmjs-unknown-emscripten`

#1591 was closed by #1697 but it was only for `wasm32-unknown-emscripten` actually. We should make a new issue and link to it instead if it's still broken.
r? `@ghost`
bors added a commit that referenced this issue Feb 10, 2021
Re-enable CI for `asmjs-unknown-emscripten`

#1591 was closed by #1697 but it was only for `wasm32-unknown-emscripten` actually. We should make a new issue and link to it instead if it's still broken.
r? `@ghost`
bors added a commit that referenced this issue Feb 10, 2021
Re-enable CI for `asmjs-unknown-emscripten`

#1591 was closed by #1697 but it was only for `wasm32-unknown-emscripten` actually. We should make a new issue and link to it instead if it's still broken.
r? `@ghost`
bors added a commit that referenced this issue Feb 10, 2021
Re-enable CI for `asmjs-unknown-emscripten`

#1591 was closed by #1697 but it was only for `wasm32-unknown-emscripten` actually. We should make a new issue and link to it instead if it's still broken.
r? `@ghost`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-CI Area: CI-related items
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant