On Linux, I got the following test failure (with or without suggested
change):
testChildProcLauncher(org.apache.spark.launcher.SparkLauncherSuite) Time
elapsed: 0.036 sec <<< FAILURE!
java.lang.AssertionError: expected:<0> but was:<1>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:555)
at org.junit.Assert.assertEquals(Assert.java:542)
at
org.apache.spark.launcher.SparkLauncherSuite.testChildProcLauncher(SparkLauncherSuite.java:113)
Has anyone seen the above before ?
Cheers
On Sat, Oct 31, 2015 at 5:20 AM, gus <gustavo.aroc...@gmail.com> wrote:
> Hi
> the SparkLauncher#setJavaHome method uses its argument to find the java
> executable, but it does not reset the JAVA_HOME env var in the child
> process. As a result, spark scripts such as bin/spark-class that rely on
> JAVA_HOME use the wrong value. Adding this to setJavaHome fixes the
> problem:
>
> builder.childEnv.put("JAVA_HOME", javaHome);
>
> Should I submit a PR for this or if someone is already working on this code
> maybe they can fix it?
>
>
>
>
> --
> View this message in context:
> http://apache-spark-developers-list.1001551.n3.nabble.com/SparkLauncher-setJavaHome-does-not-set-JAVA-HOME-in-child-process-tp14848.html
> Sent from the Apache Spark Developers List mailing list archive at
> Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org
> For additional commands, e-mail: dev-h...@spark.apache.org
>
>
