You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Benjamin Hindman (JIRA)" <ji...@apache.org> on 2013/03/12 21:43:14 UTC

[jira] [Created] (MESOS-386) AllocatorTest/0.TaskFinished has incomplete expectations.

Benjamin Hindman created MESOS-386:
--------------------------------------

             Summary: AllocatorTest/0.TaskFinished has incomplete expectations.
                 Key: MESOS-386
                 URL: https://issues.apache.org/jira/browse/MESOS-386
             Project: Mesos
          Issue Type: Bug
            Reporter: Benjamin Hindman


[ RUN      ] AllocatorTest/0.TaskFinished
../../src/tests/allocator_tests.cpp:1160: Failure
Mock function called more times than expected - returning directly.
    Function call: resourcesChanged(@0x2b7c4c02e758 201303120800-160088899-56032-25474-0000, @0x2b7c4c02e738 default, @0x2b7c4c02e700 { cpus=1, mem=256 })
         Expected: to be called twice
           Actual: called 3 times - over-saturated and active
F0312 08:00:24.401162 25507 monitor.cpp:198] Check failed: !statistics.isDiscarded()
*** Check failure stack trace: ***
    @     0x2b7c361d124d  google::LogMessage::Fail()
    @     0x2b7c361d39df  google::LogMessage::SendToLog()
    @     0x2b7c361d0e4b  google::LogMessage::Flush()
    @     0x2b7c361d426d  google::LogMessageFatal::~LogMessageFatal()
    @     0x2b7c35f28b38  mesos::internal::slave::ResourceMonitorProcess::_collect()
    @     0x2b7c35f2de5d  std::tr1::_Function_handler<>::_M_invoke()
    @     0x2b7c360ddc7d  std::tr1::function<>::operator()()
    @     0x2b7c360c41c5  process::ProcessBase::visit()
    @     0x2b7c360cb34c  process::DispatchEvent::visit()
    @     0x2b7c360c198a  process::ProcessManager::resume()
    @     0x2b7c360b8ea7  process::schedule()
    @     0x2b7c37071e9a  start_thread
    @     0x2b7c3737acbd  (unknown)
/bin/bash: line 5: 25474 Aborted                 ${dir}$tst

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira