mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "haosdent (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (MESOS-6180) Several tests are flaky, with futures timing out early
Date Sun, 18 Sep 2016 03:42:20 GMT

    [ https://issues.apache.org/jira/browse/MESOS-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15500170#comment-15500170
] 

haosdent edited comment on MESOS-6180 at 9/18/16 3:41 AM:
----------------------------------------------------------

Try to reproduce with stress in an aws instance (16 cpus, 32 gb mem, Ubuntu 14.04), but could
not reproduce after 5429 iterations as well.


was (Author: haosdent@gmail.com):
Try to reproduce with stress in an aws instance (16 cpus, 32 gb mem, Ubuntu 14.04), but could
not reproduce as well.

> Several tests are flaky, with futures timing out early
> ------------------------------------------------------
>
>                 Key: MESOS-6180
>                 URL: https://issues.apache.org/jira/browse/MESOS-6180
>             Project: Mesos
>          Issue Type: Bug
>          Components: tests
>            Reporter: Greg Mann
>            Assignee: haosdent
>              Labels: mesosphere, tests
>         Attachments: CGROUPS_ROOT_PidNamespaceBackward.log, CGROUPS_ROOT_PidNamespaceForward.log,
FetchAndStoreAndStoreAndFetch.log, flaky-containerizer-pid-namespace-backward.txt, flaky-containerizer-pid-namespace-forward.txt
>
>
> Following the merging of a large patch chain, it was noticed on our internal CI that
several tests had become flaky, with a similar pattern in the failures: the tests fail early
when a future times out. Often, this occurs when a test cluster is being spun up and one of
the offer futures times out. This has been observed in the following tests:
> * MesosContainerizerSlaveRecoveryTest.CGROUPS_ROOT_PidNamespaceForward
> * MesosContainerizerSlaveRecoveryTest.CGROUPS_ROOT_PidNamespaceBackward
> * ZooKeeperStateTest.FetchAndStoreAndStoreAndFetch
> * RoleTest.ImplicitRoleRegister
> * SlaveRecoveryTest/0.MultipleFrameworks
> * SlaveRecoveryTest/0.ReconcileShutdownFramework
> * SlaveTest.ContainerizerUsageFailure
> * MesosSchedulerDriverTest.ExplicitAcknowledgements
> * SlaveRecoveryTest/0.ReconnectHTTPExecutor (MESOS-6164)
> * ResourceOffersTest.ResourcesGetReofferedAfterTaskInfoError (MESOS-6165)
> * SlaveTest.CommandTaskWithKillPolicy (MESOS-6166)
> See the linked JIRAs noted above for individual tickets addressing a couple of these.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message