[
https://issues.apache.org/jira/browse/MESOS-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Budnik updated MESOS-5048:
---------------------------------
Attachment: ResourceStatistics-badrun3.txt
This log contains a line which might help in finding the root cause:
{code}
../../src/tests/mesos.cpp:889: Failure
(cgroups::destroy(hierarchy, cgroup)).failure(): Failed to remove cgroup
'/sys/fs/cgroup/memory/mesos_test_e7b0866c-e63a-4a0c-b810-d47d7d059b7c/8f128d76-4d34-4cd3-9dec-154a59d62977':
Device or resource busy
{code}
> MesosContainerizerSlaveRecoveryTest.ResourceStatistics is flaky
> ---------------------------------------------------------------
>
> Key: MESOS-5048
> URL: https://issues.apache.org/jira/browse/MESOS-5048
> Project: Mesos
> Issue Type: Bug
> Components: test
> Affects Versions: 0.28.0
> Environment: Ubuntu 15.04, Ubuntu 16.04
> Reporter: Jian Qiu
> Labels: flaky-test
> Attachments: ResourceStatistics-badrun2.txt,
> ResourceStatistics-badrun3.txt
>
>
> ./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.4.14#64029)
