-
- Downloads
Fix computation of classpath when we launch java directly
The previous version assumed that a CLASSPATH environment variable was set by the "run" script when launching the process that starts the ExecutorRunner, but unfortunately this is not true in tests. Instead, we factor the classpath calculation into an extenral script and call that. NOTE: This includes a Windows version but hasn't yet been tested there.
Showing
- bin/compute-classpath.cmd 52 additions, 0 deletionsbin/compute-classpath.cmd
- bin/compute-classpath.sh 89 additions, 0 deletionsbin/compute-classpath.sh
- core/src/main/scala/spark/Utils.scala 31 additions, 0 deletionscore/src/main/scala/spark/Utils.scala
- core/src/main/scala/spark/deploy/worker/ExecutorRunner.scala 3 additions, 16 deletionscore/src/main/scala/spark/deploy/worker/ExecutorRunner.scala
- run 10 additions, 57 deletionsrun
- run2.cmd 4 additions, 34 deletionsrun2.cmd
Loading
Please register or sign in to comment