[
https://issues.apache.org/jira/browse/MESOS-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13747271#comment-13747271
]
Benjamin Mahler commented on MESOS-652:
---------------------------------------
I don't believe it was, this was on a beefy server machine. That said, I can't
reproduce this because I'm unable to run the recovery tests with a high number
of iterations:
../../src/tests/mesos.cpp:164: Failure
(cgroups::cleanup(TEST_CGROUPS_HIERARCHY)).failure(): Failed to remove cgroup
'/tmp/mesos_test_cgroup/mesos_test/framework_201308220555-2081170186-41554-37964-0000_executor_9fcfeb18-317f-466a-9f5b-d203e2926c18_tag_c6e0103e-6e6b-430c-bfd3-eaff7fb8dfff':
Device or resource busy
Were you able to do so?
> SlaveRecoveryTest/0.ShutdownSlave is flaky (hangs forever).
> -----------------------------------------------------------
>
> Key: MESOS-652
> URL: https://issues.apache.org/jira/browse/MESOS-652
> Project: Mesos
> Issue Type: Bug
> Reporter: Benjamin Mahler
> Assignee: Vinod Kone
>
> Observed this on a Linux machine.
> [ RUN ] SlaveRecoveryTest/0.ShutdownSlave
> Checkpointing forked pid 7698 to
> '/tmp/SlaveRecoveryTest_0_ShutdownSlave_G7nzp1/meta/slaves/201308210309-2081170186-49605-5676-0/frameworks/201308210309-2081170186-49605-5676-0000/executors/2968d586-77ae-4fce-8dd7-9a8dec69791a/runs/91b77f8a-d78d-491a-99d9-bfbbe0cbba8a/pids/forked.pid'
> Fetching resources into
> '/tmp/SlaveRecoveryTest_0_ShutdownSlave_G7nzp1/slaves/201308210309-2081170186-49605-5676-0/frameworks/201308210309-2081170186-49605-5676-0000/executors/2968d586-77ae-4fce-8dd7-9a8dec69791a/runs/91b77f8a-d78d-491a-99d9-bfbbe0cbba8a'
> Registered executor on smfd-aki-27-sr1.devel.twitter.com
> Starting task 2968d586-77ae-4fce-8dd7-9a8dec69791a
> sh -c 'sleep 1000'
> Forked command at 7744
> ../../src/tests/slave_recovery_tests.cpp:1370: Failure
> Failed to wait 10secs for statusUpdate1
> Shutting down
> Command terminated with signal Killed (pid: 7697)
> At which point, the test hangs forever.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
