Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120583285
Oh odd I didn't see that in the test output, just saw thrift test returned
-1.
Let me try to repro.
> On Jul 10, 2015, at 10:25 PM, andrewor14 <notificati...@github.com> wrote:
>
> Are you sure it's not related? The test failure is:
>
>
org.apache.spark.scheduler.cluster.mesos.CoarseMesosSchedulerBackendSuite.(It
is not a test)
>
> Error Message
>
> no mesos in java.library.path
> Stacktrace
>
> sbt.ForkMain$ForkError: no mesos in java.library.path
> at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1886)
> at java.lang.Runtime.loadLibrary0(Runtime.java:849)
> at java.lang.System.loadLibrary(System.java:1088)
> at
org.apache.mesos.MesosNativeLibrary.load(MesosNativeLibrary.java:54)
> at
org.apache.mesos.MesosNativeLibrary.load(MesosNativeLibrary.java:79)
> at
org.apache.mesos.MesosSchedulerDriver.<clinit>(MesosSchedulerDriver.java:61)
> at
org.apache.spark.scheduler.cluster.mesos.MesosSchedulerUtils$class.createSchedulerDriver(MesosSchedulerUtils.scala:94)
> at
org.apache.spark.scheduler.cluster.mesos.CoarseMesosSchedulerBackend.createSchedulerDriver(CoarseMesosSchedulerBackend.scala:46)
> â
> Reply to this email directly or view it on GitHub.
>
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
