mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Rukletsov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-7506) Multiple tests leave orphan containers.
Date Tue, 07 Nov 2017 16:09:01 GMT

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

Alexander Rukletsov updated MESOS-7506:
---------------------------------------
    Description: 
I've observed a number of flaky tests that leave orphan containers upon cleanup. A typical
log looks like this:
{noformat}
../../src/tests/cluster.cpp:580: Failure
Value of: containers->empty()
  Actual: false
Expected: true
Failed to destroy containers: { da3e8aa8-98e7-4e72-a8fd-5d0bae960014 }
{noformat}

All currently affected tests:
{noformat}
ROOT_DOCKER_DockerAndMesosContainerizers/DefaultExecutorTest.KillTask/0
ROOT_DOCKER_DockerAndMesosContainerizers/DefaultExecutorTest.TaskWithFileURI/0
ROOT_DOCKER_DockerAndMesosContainerizers/DefaultExecutorTest.ResourceLimitation/0
ROOT_DOCKER_DockerAndMesosContainerizers/DefaultExecutorTest.KillMultipleTasks/0
SlaveRecoveryTest/0.RecoverUnregisteredExecutor
SlaveRecoveryTest/0.CleanupExecutor
SlaveRecoveryTest/0.RecoverTerminatedExecutor
SlaveTest.ShutdownUnregisteredExecutor
ShutdownUnregisteredExecutor
{noformat}

  was:
I've observed a number of flaky tests that leave orphan containers upon cleanup. A typical
log looks like this:
{noformat}
../../src/tests/cluster.cpp:580: Failure
Value of: containers->empty()
  Actual: false
Expected: true
Failed to destroy containers: { da3e8aa8-98e7-4e72-a8fd-5d0bae960014 }
{noformat}

All currently affected tests:
{noformat}
ROOT_DOCKER_DockerAndMesosContainerizers/DefaultExecutorTest.KillTask/0
ROOT_DOCKER_DockerAndMesosContainerizers/DefaultExecutorTest.TaskWithFileURI/0
ROOT_DOCKER_DockerAndMesosContainerizers/DefaultExecutorTest.ResourceLimitation/0
SlaveRecoveryTest/0.RecoverUnregisteredExecutor
SlaveRecoveryTest/0.CleanupExecutor
SlaveRecoveryTest/0.RecoverTerminatedExecutor
SlaveTest.ShutdownUnregisteredExecutor
ShutdownUnregisteredExecutor
{noformat}


> Multiple tests leave orphan containers.
> ---------------------------------------
>
>                 Key: MESOS-7506
>                 URL: https://issues.apache.org/jira/browse/MESOS-7506
>             Project: Mesos
>          Issue Type: Bug
>          Components: containerization
>         Environment: Ubuntu 16.04
> Fedora 23
> other Linux distros
>            Reporter: Alexander Rukletsov
>            Assignee: Andrei Budnik
>              Labels: containerizer, flaky-test, mesosphere
>         Attachments: ResourceLimitation-badrun.txt, TaskWithFileURI-badrun.txt
>
>
> I've observed a number of flaky tests that leave orphan containers upon cleanup. A typical
log looks like this:
> {noformat}
> ../../src/tests/cluster.cpp:580: Failure
> Value of: containers->empty()
>   Actual: false
> Expected: true
> Failed to destroy containers: { da3e8aa8-98e7-4e72-a8fd-5d0bae960014 }
> {noformat}
> All currently affected tests:
> {noformat}
> ROOT_DOCKER_DockerAndMesosContainerizers/DefaultExecutorTest.KillTask/0
> ROOT_DOCKER_DockerAndMesosContainerizers/DefaultExecutorTest.TaskWithFileURI/0
> ROOT_DOCKER_DockerAndMesosContainerizers/DefaultExecutorTest.ResourceLimitation/0
> ROOT_DOCKER_DockerAndMesosContainerizers/DefaultExecutorTest.KillMultipleTasks/0
> SlaveRecoveryTest/0.RecoverUnregisteredExecutor
> SlaveRecoveryTest/0.CleanupExecutor
> SlaveRecoveryTest/0.RecoverTerminatedExecutor
> SlaveTest.ShutdownUnregisteredExecutor
> ShutdownUnregisteredExecutor
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message