Stream: t-compiler

Topic: how to run ui tests against wasm target?

David Haig (Nov 28 2019 at 16:05, on Zulip):

Hi guys, not sure if this is the right group but Oli recommended that I ask a question on the compiler channel. Does anyone know how to manually run the ui tests against a wasm target build? This is the only documentation I have been able to find about it:

I am asking because some new unit tests I added are breaking the tests that run against this target on azure. The tests break because I am using async and I was using compiler flags instead of setting the edition:2018 in the test. At least I believe that this is the issue but I cannot confirm it until I can run those tests manually.

pnkfelix (Nov 28 2019 at 16:06, on Zulip):

(I renamed your topic)

David Haig (Nov 28 2019 at 16:08, on Zulip):

Thanks! This relates to this PR:

eddyb (Nov 28 2019 at 16:13, on Zulip):

you might be able to just pass the right --target flag to ./ test --stage 1 src/test/ui

eddyb (Nov 28 2019 at 16:14, on Zulip):

I know building std for both the host and the wasm target is really easy (as I've had to do it a bunch recently) so I'm hoping this also works

eddyb (Nov 28 2019 at 16:15, on Zulip):

@David Haig I was going to say "this works" for ./ test --stage 1 src/test/ui --target wasm32-unknown-unknown but I'm getting a lot of F's oops

eddyb (Nov 28 2019 at 16:15, on Zulip):

curious what it will be, maybe I'm just missing a runtime dependency?

eddyb (Nov 28 2019 at 16:18, on Zulip):
[ERROR compiletest::runtest] fatal error, panic: "no NodeJS binary found (--nodejs)"
eddyb (Nov 28 2019 at 16:19, on Zulip):

@David Haig yeah so make sure you have node.js installed and then run the command above

David Haig (Nov 28 2019 at 16:24, on Zulip):

@eddyb Ok I'll give that a go, cheers!

Last update: May 27 2020 at 23:10UTC