It could pass in my env. May you post the log of
```
$ GLOG_v=1 ./bin/mesos-tests.sh
--gtest_filter="*CommandExecutorTest.NoTaskKillingCapability*" --verbose
```

On Wed, Jun 29, 2016 at 2:05 PM, pangbingqiang <[email protected]>
wrote:

> Hi all:
>
>    Recently I run mesos tests on my machine, when I run*
> “CommandExecutorTest.NoTaskKillingCapability”* this test case, there will
>
> Have error. Log is as follow:
>
> *  >[ RUN      ] CommandExecutorTest.NoTaskKillingCapability*
>
> *>I0629 13:56:20.119189 118953 exec.cpp:143] Version: 0.28.2*
>
> *>tests/command_executor_tests.cpp:95: Failure*
>
> *>Failed to wait 15secs for statusRunning*
>
> *>tests/command_executor_tests.cpp:90: Failure*
>
> *>Actual function call count doesn't match EXPECT_CALL(sched,
> statusUpdate(_, _))...*
>
> *  >       Expected: to be called once*
>
> *  >         Actual: never called - unsatisfied and active*
>
> *>[  FAILED  ] CommandExecutorTest.NoTaskKillingCapability (15324 ms) *
>
>
>
> It seem that statusUpdate do not called, I don’t why, my mesos version is
> 0.28.2?
>
> [image: cid:[email protected]]
>
>
>
> Bingqiang Pang(庞兵强)
>
>
>
> Distributed and Parallel Software Lab
>
> Huawei Technologies Co., Ltd.
>
> Email:[email protected] <[email protected]>
>
>
>
>
>



-- 
Best Regards,
Haosdent Huang

Reply via email to