[ 
https://issues.apache.org/jira/browse/MESOS-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhitao Li updated MESOS-7381:
-----------------------------
    Description: 
See https://gist.github.com/zhitaoli/40aacc3f2ecb88802ee58f40c46d43f9 for a log.

There are about 12-13 tests in that class which are very flaky in my 
environment (Debian/jessie running 4.4.38 kernel).

It seems like the primary cause is that root container "failed" and caused 
`reap` to be called on itself, which cascalade and cause both containers to be 
actively killed by containerizer instead of terminate by themselves.

  was:
See https://gist.github.com/zhitaoli/676457f6f71196057d08942d7b79019e for a log.

It seems like the parent container was reaped before the wait call on the 
nested container's, therefore the nested container was killed instead of 
terminated by itself.

        Summary: Flaky tests in NestedMesosContainerizerTest  (was: Flaky test 
for NestedMesosContainerizerTest.ROOT_CGROUPS_LaunchNested)

> Flaky tests in NestedMesosContainerizerTest
> -------------------------------------------
>
>                 Key: MESOS-7381
>                 URL: https://issues.apache.org/jira/browse/MESOS-7381
>             Project: Mesos
>          Issue Type: Bug
>          Components: test
>            Reporter: Zhitao Li
>
> See https://gist.github.com/zhitaoli/40aacc3f2ecb88802ee58f40c46d43f9 for a 
> log.
> There are about 12-13 tests in that class which are very flaky in my 
> environment (Debian/jessie running 4.4.38 kernel).
> It seems like the primary cause is that root container "failed" and caused 
> `reap` to be called on itself, which cascalade and cause both containers to 
> be actively killed by containerizer instead of terminate by themselves.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to