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

Set up CI testing for asm.js and wasm #38801

Closed
brson opened this Issue Jan 3, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@brson
Copy link
Contributor

brson commented Jan 3, 2017

asm.js and wasm targets only have build CI today. They need tests to be run as well in order to maintain decent support.

I think there's a good chance we will lose asm.js support, at least temporarily, when we switch to the LLVM wasm backend, but as long as we do support asm.js we might as well test it too.

This should be a matter of changing the travis config to run the tests in a new container.

@brson

This comment has been minimized.

Copy link
Contributor Author

brson commented Jan 27, 2017

@alexcrichton has done some work on this.

@alexcrichton

This comment has been minimized.

Copy link
Member

alexcrichton commented Mar 23, 2017

This is done now for emscripten! When wasm tests are passing we can set up CI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.