Yes, it is set exactly as you pointed out - /usr/local/lib/libmesos.so
Just in case adding jre info:
vagrant@master:/vagrant$ echo $JAVA_HOME
/usr/lib/jvm/java-7-openjdk-amd64/jre
vagrant@master:/vagrant$ java -version
java version "1.7.0_95"
OpenJDK Runtime Environment (IcedTea 2.6.4)
Hi, do you try to set MESOS_NATIVE_JAVA_LIBRARY=/usr/local/lib/libmesos.so ?
On Thu, Feb 18, 2016 at 6:34 AM, Andrii Biletskyi <
andrii.bilets...@stealth.ly> wrote:
> Hi all,
>
> I'm trying to test new networking module. In order to do that I built
> mesos from tag 0.27.0
> with unbundled
+1 (non binding)
Debian 8 (jessie) plain non root OK.
Mac OS X plain non root OK.
Ubuntu 14.04 plain/SSL with root and docker-engine 1.10: Only flaky test I
observed on Ubuntu 14.04 is HealthCheckTest.HealthStatusChange, which is
tracked in MESOS-1802 already.
> On Feb 17, 2016, at 5:21 AM,
Hi all,
I'm trying to test new networking module. In order to do that I built mesos
from tag 0.27.0
with unbundled dependencies as suggested. I pretty much followed this
Dockerfile
https://github.com/mesosphere/docker-containers/blob/master/mesos-modules-dev/Dockerfile
.
I'm doing all the steps
+1 (binding)
Test failures look a lot like with 0.27.0. Not clean, but nothing deemed too
drastic yet.
CentOS 7 plain:
FetcherCacheHttpTest.HttpCachedSerialized flaky again, filed MESOS-4692
LinuxFilesystemIsolatorTest.ROOT_ImageInVolumeWithRootFilesystem known as
flaky: MESOS-4674
5 matches
Mail list logo