[
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.
This happens on master branch at commit 6c1e20c0f2777d9bb831be3ff43c885b253af7bb
was:
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.
> 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 happens on master branch at commit
> 6c1e20c0f2777d9bb831be3ff43c885b253af7bb
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)