[
https://issues.apache.org/jira/browse/MESOS-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15233034#comment-15233034
]
Greg Mann commented on MESOS-5048:
----------------------------------
[~qiujian], thus far I've been unable to reproduce this failure. I've been
running it on Ubuntu 14.04 - I see you specified the environment as Ubuntu
15.04, is that what you're running on your local machine? RB runs the reviewbot
on Ubuntu 14.04, so if you saw the failure on RB, I would expect it to be
reproducible on 14.04 as well.
Did you use simply {{../configure}}, with no arguments, to configure your build?
> MesosContainerizerSlaveRecoveryTest.ResourceStatistics is flaky
> ---------------------------------------------------------------
>
> Key: MESOS-5048
> URL: https://issues.apache.org/jira/browse/MESOS-5048
> Project: Mesos
> Issue Type: Bug
> Components: tests
> Affects Versions: 0.28.0
> Environment: Ubuntu 15.04
> Reporter: Jian Qiu
> Labels: flaky-test
>
> ./mesos-tests.sh
> --gtest_filter=MesosContainerizerSlaveRecoveryTest.ResourceStatistics
> --gtest_repeat=100 --gtest_break_on_failure
> This is found in rb, and reproduced in my local machine. There are two types
> of failures. However, the failure does not appear when enabling verbose...
> {code}
> ../../src/tests/environment.cpp:790: Failure
> Failed
> Tests completed with child processes remaining:
> -+- 1446 /mesos/mesos-0.29.0/_build/src/.libs/lt-mesos-tests
> \-+- 9171 sh -c /mesos/mesos-0.29.0/_build/src/mesos-executor
> \--- 9185 /mesos/mesos-0.29.0/_build/src/.libs/lt-mesos-executor
> {code}
> And
> {code}
> I0328 15:42:36.982471 5687 exec.cpp:150] Version: 0.29.0
> I0328 15:42:37.008765 5708 exec.cpp:225] Executor registered on slave
> 731fb93b-26fe-4c7c-a543-fc76f106a62e-S0
> Registered executor on mesos
> ../../src/tests/slave_recovery_tests.cpp:3506: Failure
> Value of: containers.get().size()
> Actual: 0
> Expected: 1u
> Which is: 1
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
