[
https://issues.apache.org/jira/browse/MESOS-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15412667#comment-15412667
]
Benjamin Mahler commented on MESOS-5889:
----------------------------------------
[~neilc] we try to include good vs bad logs in flaky test reports as it lowers
the barrier to looking into the issue (don't need to go digging around CI or
compile / run it locally to get logs for a good run). For example: MESOS-4800.
> Flakiness in SlaveRecoveryTest
> ------------------------------
>
> Key: MESOS-5889
> URL: https://issues.apache.org/jira/browse/MESOS-5889
> Project: Mesos
> Issue Type: Bug
> Components: tests
> Reporter: Neil Conway
> Labels: mesosphere
> Attachments: slave_recovery_cleanup_http_executor.log,
> slave_recovery_recover_terminated_executor.log,
> slave_recovery_recover_unregistered_http_executor.log
>
>
> Observed on internal CI. Seems like it is related to cgroups? Observed
> similar failures in the following tests, and probably more related tests:
> SlaveRecoveryTest/0.CleanupHTTPExecutor
> SlaveRecoveryTest/0.RecoverUnregisteredHTTPExecutor
> SlaveRecoveryTest/0.RecoverTerminatedExecutor
> Log files attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
