Hello, I have a standalone install of mesos running on a capable box (running Centos 6.2), but running into issues with the sanity test (make check).
The initial failure is: [ RUN ] CoordinatorTest.MultipleAppendsNotLearnedFill ../../src/tests/log_tests.cpp:860: Failure Value of: result.isSome() Actual: false Expected: true [ FAILED ] CoordinatorTest.MultipleAppendsNotLearnedFill (2295 ms) [ RUN ] CoordinatorTest.Truncate # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x0000000001ed0ab8, pid=8514, tid=140213985802016 In the mailing list archives, I found a similar problem faced by another user: http://mail-archives.apache.org/mod_mbox/incubator-mesos-dev/201205.mbox/%3CCAKOYTn9Td-Ru487aLnqrApKtvo2QuEb77Zt459_WPff2eLrVCQ%40mail.gmail.com%3E As suggested in that thread, the problem seems to be with the test on my box taking longer than what the test expects, and increasing the timeout in the test to 3s or 4s makes the failures above go away. However, other tests continue to fail like CoordinatorTest.MultipleAppends, CoordinatorTest.TruncateNotLearnedFill, CoordinatorTest.TruncateLearnedFill. I had to increase the timeouts on all these tests to get make check to succeed. I am evaluating mesos for production use, and I am concerned about the reason for these tests taking longer than expected. Any help would be appreciated. My environment/config: Centos 6.2, 64-bit Kernel: 2.6.32-220.el6.x86_64 CPU: 24 (Intel(R) Xeon(R) CPU L5640 @ 2.27GHz) RAM: 16 GB Thanks, Arindam
