-
Notifications
You must be signed in to change notification settings - Fork 59
Use the executable "nodejs" when testing Scala.js. #276
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
Conversation
Would it be possible to launch a community build for this PR, so that we can test in advance whether switching to Node.js by default will be fine on this CI infrastructure? (The PR should not be merged, even if successful; the default will simply change in Scala.js master so it will eventually apply here.) |
Yes, we can! |
https://scala-ci.typesafe.com/job/scala-2.11.x-integrate-community-build/294/ says:
I guess you want us to install |
Yes, that would be nice, if it isn't too problematic on your side. FTR on our workers we test with Node.js 4.2.1. Any version at least as recent should work. |
Hmm, I spoke too soon, I guess. How hard is it to get a node.js environment up and running? If it's just a matter of apt-get install, we could look into it this week I guess, otherwise it may have to wait a week or two. |
It should be just an apt-get install, assuming the distribution contains a recent enough version of Node.js. |
Any news about this, now that RC1 is out? |
for Scala.js. requested by @sjrd at scala/community-build#276
for Scala.js. requested by @sjrd at scala/community-build#276
for Scala.js. requested by @sjrd at scala/community-build#276
8679560
to
c182410
Compare
Updated with setting the name of the executable to ( |
https://scala-ci.typesafe.com/job/scala-2.11.x-integrate-community-build/302/consoleFull failed with
but it passes (locally) if I add
want to throw that in & I'll merge? I'm sure I could figure out whatever additional Chef stuff would be needed to get |
c182410
to
80ef017
Compare
Sure, done :) |
Scala.js will change its default runner from Rhino to Node.js in 0.6.13 (see scala-js/scala-js#2579). By default, it looks for an executable called `"node"`, but on the community build infrastructure, Node.js is called `"nodejs"`. This commit instructs Scala.js to use `"nodejs"` instead.
Thanks! |
@sjrd it isn't working, https://scala-ci.typesafe.com/job/scala-2.11.x-integrate-community-build/307/consoleFull shows:
|
Ah! The community build is trying to run the tests of all the projects that need to be compiled, instead of only the projects listed. That's weird, but whatever. So it's trying to run the test for Well, I guess a follow up PR is coming. |
Scala.js will change its default runner from Rhino to Node.js in 0.6.13 (see scala-js/scala-js#2579). This commit preemptively tests whether this is going to be a problem for the community build.