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

Tool support for testing wasm targets #38803

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

Comments

Projects
None yet
4 participants
@brson
Copy link
Contributor

brson commented Jan 3, 2017

In order to make the wasm targets production ready we'll need a testing solution. Right now I'm inclined to teach cross how to do it and call that the solution, but that excludes macOS hosts, and for now at least, Windows as well, since it relies on docker.

cc @japaric

@brson brson referenced this issue Jan 3, 2017

Closed

Tracking issue for wasm support #38805

11 of 15 tasks complete
@japaric

This comment has been minimized.

Copy link
Member

japaric commented Jan 4, 2017

Right now I'm inclined to teach cross

See rust-lang/cross#36. If rustc emitted executable .js files with a #!/usr/bin/env node shebang in them then cross test would work for the asmjs target. I'm not sure what else would need to be done for the wasm target though because node hello-wasm.js errors with node v7.3.0 as stated in that PR.

@Mark-Simulacrum Mark-Simulacrum added T-dev-tools and removed T-tools labels May 24, 2017

@alexcrichton

This comment has been minimized.

Copy link
Member

alexcrichton commented Oct 18, 2017

I believe we've since implemented the "runner" configuration in Cargo, which I believe solves this.

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.