Uploaded image for project: 'Mesos'
  1. Mesos
  2. MESOS-7916

Improve the test coverage of the DefaultExecutor.

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.5.0
    • executor
    • Mesosphere Sprint 62, Mesosphere Sprint 63, Mesosphere Sprint 64, Mesosphere Sprint 65
    • 5

    Description

      We should write tests for the DefaultExecutor to cover the following common scenarios:

      1. Start a task that uses a GPU, and make sure that it is made available to the task.
      2. Launch a Docker task with a health check.
      3. Launch two tasks and verify that they can access a volume owned by the Executor via sandbox_path volumes.
      4. 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.
      5. Launch a task that uses an env secret, make sure that it is accessible.
      6. Launch a task using a URI and make sure that the artifact is accessible.
      7. Launch a task using a Docker image + URIs, make sure that the fetched artifact is accessible.
      8. Launch one task and ensure that (health) checks can read from a persistent volume.
      9. Ensure that the executor's env is NOT inherited by the nested tasks.

      Attachments

        Issue Links

          Activity

            People

              gkleiman Gastón Kleiman
              gkleiman Gastón Kleiman
              Greg Mann Greg Mann
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: