[
https://issues.apache.org/jira/browse/MESOS-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14636987#comment-14636987
]
Tony Reix commented on MESOS-2216:
----------------------------------
- Tests on Ubuntu/i386/pxi3270_27sr3-20150415_01(SR3) : 32bits IBM JVM
[ RUN ] DurationTest.Arithmetic
../../../../3rdparty/libprocess/3rdparty/stout/tests/duration_tests.cpp:66:
Failure
Value of: Seconds(10) * 0.33
Actual: 3300ms
Expected: Duration::create(3.3).get()
Which is: 3.299999999secs
- Tests on Ubuntu/x86_64/IBMJVM-1.7.0-pxa6470_27sr3-20150415_01(SR3) : 64bits
IBM JVM:
[==========] 454 tests from 71 test cases ran. (243196 ms total)
[ PASSED ] 450 tests.
[ FAILED ] 4 tests, listed below:
[ FAILED ] ResourcesTest.Parsing
[ FAILED ] ResourcesTest.Resources
[ FAILED ] ValuesTest.ValidInput
[ FAILED ] PerfTest.Parse
- RHEL7 on PPC64 LE :
Cannot test patch and configure since error cannot be fixed:
libsubversion-1 is required for mesos to build.
> The "configure" phase breaks with the IBM JVM.
> ----------------------------------------------
>
> Key: MESOS-2216
> URL: https://issues.apache.org/jira/browse/MESOS-2216
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 0.20.1, 1.0.0
> Environment: Ubuntu / x86_64
> Reporter: Tony Reix
> Attachments: MESOS-2216_1.patch, MESOS-2216_2.patch, config.log,
> jniport.h, x86_64_traces
>
>
> ./configure does not work with IBM JVM, since it looks for a directory:
> /usr/lib/jvm/ibm-java-x86_64-71/jre/lib/amd64/server x86_64
> /usr/lib/jvm/ibm-java-ppc64le-71/jre/lib/ppc64le/server PPC64 LE
> that does not exist for the IBM JVM.
> Though this directory does exist for Oracle JVM and Open JDK:
> /usr/lib/jvm/jdk1.7.0_71/jre/lib/amd64/server Oracle JVM
> /usr/lib/jvm/java-1.7.0-openjdk-amd64/jre/lib/amd64/server OpenJDK
> However, the files:
> libjsig.so
> libjvm.so (3 versions)
> do exist for IBM JVM.
> Anyway, creating the server directory and copying the files (tried with the 3
> versions of libjvm.so) does not fix the issue:
> checking whether or not we can build with JNI...
> /usr/lib/jvm/ibm-java-x86_64-71/jre/lib/amd64/server/libjvm.so: undefined
> reference to `dlopen'
> /usr/lib/jvm/ibm-java-x86_64-71/jre/lib/amd64/server/libjvm.so: undefined
> reference to `dlclose'
> /usr/lib/jvm/ibm-java-x86_64-71/jre/lib/amd64/server/libjvm.so: undefined
> reference to `dlerror'
> /usr/lib/jvm/ibm-java-x86_64-71/jre/lib/amd64/server/libjvm.so: undefined
> reference to `dlsym'
> /usr/lib/jvm/ibm-java-x86_64-71/jre/lib/amd64/server/libjvm.so: undefined
> reference to `dladdr'
> Something (dlopen, dlclose, dlerror, dlsym, dladdr) is missing in IBM JVM.
> So, either the configure step relies on a feature that is not in the Java
> standard but only in the Oracle JVM and OpenJDK, or the IBM JVM lacks part of
> the Java standard.
> I'm not an expert about this. So, I'd like Mesos people to experiment with
> IBM JVM. Maybe there is another solution for this step of the Mesos configure
> that would work with all 3 JVMs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
