You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Gastón Kleiman (JIRA)" <ji...@apache.org> on 2017/08/24 23:15:01 UTC

[jira] [Commented] (MESOS-7916) Improve the test coverage of the DefaultExecutor.

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

Gastón Kleiman commented on MESOS-7916:
---------------------------------------

https://reviews.apache.org/r/61282/
https://reviews.apache.org/r/61438/
https://reviews.apache.org/r/61483/

> Improve the test coverage of the DefaultExecutor.
> -------------------------------------------------
>
>                 Key: MESOS-7916
>                 URL: https://issues.apache.org/jira/browse/MESOS-7916
>             Project: Mesos
>          Issue Type: Improvement
>          Components: executor
>            Reporter: Gastón Kleiman
>            Assignee: Gastón Kleiman
>              Labels: mesosphere
>
> We should write tests for the {{DefaultExecutor}} to cover the following common scenarios:
> # Start a task that uses a GPU, and make sure that it is made available to the task.
> # Launch a Docker task with a health check.
> # Launch two tasks and verify that they can access a volume owned by the Executor via {{sandbox_path}} volumes.
> # Launch two tasks, each one in its own task group, and verify that they can access a volume owned by the Executor via {{sandbox_path}} volumes.
> # Launch one task and ensure that (health) checks can read from a persistent volume.
> # Launch a task using a URI and make sure that the artifact is accessible.
> # Launch a task using a Docker image + URIs, make sure that the fetched artifact is accessible.
> # Write a test that ensures that the executor's env is NOT inherited by the nested tasks.
> # Launch a task that uses an env secret, make sure that it is accessible.



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