Is that test always failing or just flaky? We have had flaky tests in the past. Good news is, we did a complete overhaul of tests in 0.13.0 (not yet released) and so far they look very stable.
On Thu, May 30, 2013 at 7:39 PM, Jean-Sebastien Delfino < [email protected]> wrote: > Hi, > > I'm trying to run the Mesos tests from the mesos-0.11.0-incubating.tar.gz > RC3 archive on Mac OS X 10.8.3 + Xcode 4.6.1, and getting a failure with a > core dump. > ./configure --disable-java > --prefix=/Users/jsdelfino/sandbox/mesos-0.11.0-bin > make > make check > gives me this: > ... > [ RUN ] MasterTest.RecoverResources > libc++abi.dylib: pure virtual method called > /bin/sh: line 1: 51021 Abort trap: 6 (core dumped) > ${dir}$tst > FAIL: mesos-tests > ... > > Any idea of what could go wrong? Thanks! > > - Jean-Sebastien > > === > Complete make check log: > > make check > Making check in . > make[1]: Nothing to be done for `check-am'. > Making check in third_party > make check-recursive > Making check in libprocess > Making check in third_party > make check-am > make libgmock.la > make[6]: `libgmock.la' is up to date. > Making check in . > make tests > make[5]: `tests' is up to date. > make libgmock.la > make[4]: `libgmock.la' is up to date. > Making check in src > make check-am > make test-framework test-executor long-lived-framework long-lived-executor > no-executor-framework balloon-framework balloon-executor mesos-tests > examples/python/test_framework.py examples/python/test-framework > examples/python/test_executor.py examples/python/test-executor \ > tests/balloon_framework_test.sh tests/test_framework_test.sh > tests/no_executor_framework_test.sh tests/java_exception_test.sh > tests/java_framework_test.sh tests/python_framework_test.sh > tests/killtree_test.sh > make[3]: `test-framework' is up to date. > make[3]: `test-executor' is up to date. > make[3]: `long-lived-framework' is up to date. > make[3]: `long-lived-executor' is up to date. > make[3]: `no-executor-framework' is up to date. > make[3]: `balloon-framework' is up to date. > make[3]: `balloon-executor' is up to date. > make[3]: `mesos-tests' is up to date. > make[3]: Nothing to be done for `examples/python/test_framework.py'. > make[3]: Nothing to be done for `examples/python/test-framework'. > make[3]: Nothing to be done for `examples/python/test_executor.py'. > make[3]: Nothing to be done for `examples/python/test-executor'. > make[3]: Nothing to be done for `tests/balloon_framework_test.sh'. > make[3]: Nothing to be done for `tests/test_framework_test.sh'. > make[3]: Nothing to be done for > `tests/no_executor_framework_test.sh'. > make[3]: Nothing to be done for `tests/java_exception_test.sh'. > make[3]: Nothing to be done for `tests/java_framework_test.sh'. > make[3]: Nothing to be done for `tests/python_framework_test.sh'. > make[3]: Nothing to be done for `tests/killtree_test.sh'. > make check-TESTS > Source directory: /Users/jsdelfino/sandbox/mesos-0.11.0 > Build directory: /Users/jsdelfino/sandbox/mesos-0.11.0 > [==========] Running 182 tests from 34 test cases. > [----------] Global test environment set-up. > [----------] 10 tests from MasterTest > [ RUN ] MasterTest.TaskRunning > [ OK ] MasterTest.TaskRunning (55 ms) > [ RUN ] MasterTest.ShutdownFrameworkWhileTaskRunning > [ OK ] MasterTest.ShutdownFrameworkWhileTaskRunning (42 ms) > [ RUN ] MasterTest.KillTask > [ OK ] MasterTest.KillTask (62 ms) > [ RUN ] MasterTest.StatusUpdateAck > [ OK ] MasterTest.StatusUpdateAck (57 ms) > [ RUN ] MasterTest.RecoverResources > libc++abi.dylib: pure virtual method called > /bin/sh: line 1: 51021 Abort trap: 6 (core dumped) > ${dir}$tst > FAIL: mesos-tests > =================== > 1 of 1 tests failed > =================== > make[3]: *** [check-TESTS] Error 1 > make[2]: *** [check-am] Error 2 > make[1]: *** [check] Error 2 > make: *** [check-recursive] Error 1 >
