Till Toenshoff created MESOS-1729:
-------------------------------------

             Summary: LogZooKeeperTest.WriteRead fails on OSX
                 Key: MESOS-1729
                 URL: https://issues.apache.org/jira/browse/MESOS-1729
             Project: Mesos
          Issue Type: Bug
          Components: build, test
    Affects Versions: 0.21.0
         Environment: OSX 10.9.4, clang 3.4
            Reporter: Till Toenshoff


The following is reported and 100% reproducible when running {{make check}} on 
my OSX box.

{noformat}
[ RUN      ] LogZooKeeperTest.WriteRead
W0821 12:36:35.715975 1914815248 glog.hpp:52] RAW: Received signal SIGPIPE; 
escalating to SIGABRT
*** Aborted at 1408617395 (unix time) try "date -d @1408617395" if you are 
using GNU date ***
PC: @     0x7fff8523b292 __kill
*** SIGABRT (@0x7fff8523b292) received by PID 90142 (TID 0x7fff7221c310) stack 
trace: ***
    @     0x7fff8a2905aa _sigtramp
    @     0x7fff7276f338 usual
    @        0x10e35737d os::Bsd::chained_handler()
    @        0x10e35b166 JVM_handle_bsd_signal
    @     0x7fff8a2905aa _sigtramp
    @                0x0 (unknown)
    @        0x10bbec97b process::ProcessManager::wait()
    @        0x10bbee96b process::wait()
    @        0x10baf062a mesos::internal::log::Log::~Log()
    @        0x10a63857a LogZooKeeperTest_WriteRead_Test::TestBody()
    @        0x10a9bff8c 
testing::internal::HandleExceptionsInMethodIfSupported<>()
    @        0x10a9ab90a testing::Test::Run()
    @        0x10a9ac592 testing::TestInfo::Run()
    @        0x10a9acbd0 testing::TestCase::Run()
    @        0x10a9b2425 testing::internal::UnitTestImpl::RunAllTests()
    @        0x10a9c0754 
testing::internal::HandleExceptionsInMethodIfSupported<>()
    @        0x10a9b2159 testing::UnitTest::Run()
    @        0x10a66ea33 main
    @     0x7fff8c1c65fd start
    @                0x1 (unknown)
make[3]: *** [check-local] Abort trap: 6
make[2]: *** [check-am] Error 2
make[1]: *** [check] Error 2
make: *** [check-recursive] Error 1
{noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to