[jira] [Updated] (MESOS-6475) Mesos Container Attach/Exec Unit Tests
[ https://issues.apache.org/jira/browse/MESOS-6475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-6475: - Sprint: Mesosphere Sprint 48, Mesosphere Sprint 49 (was: Mesosphere Sprint 48) > Mesos Container Attach/Exec Unit Tests > -- > > Key: MESOS-6475 > URL: https://issues.apache.org/jira/browse/MESOS-6475 > Project: Mesos > Issue Type: Task > Components: tests >Reporter: Kevin Klues >Assignee: Kevin Klues > Labels: debugging, mesosphere > > Ideally, all unit tests should be written as the individual tasks that make > up this Epic are completed. However, sometime this doesn't always happen as > planned. > This ticket should not be closed and the Epic should not be considered > complete until all unit tests for all components have been written. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-6475) Mesos Container Attach/Exec Unit Tests
[ https://issues.apache.org/jira/browse/MESOS-6475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-6475: - Shepherd: Vinod Kone > Mesos Container Attach/Exec Unit Tests > -- > > Key: MESOS-6475 > URL: https://issues.apache.org/jira/browse/MESOS-6475 > Project: Mesos > Issue Type: Task > Components: tests >Reporter: Kevin Klues >Assignee: Kevin Klues > Labels: debugging, mesosphere > > Ideally, all unit tests should be written as the individual tasks that make > up this Epic are completed. However, sometime this doesn't always happen as > planned. > This ticket should not be closed and the Epic should not be considered > complete until all unit tests for all components have been written. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-6475) Mesos Container Attach/Exec Unit Tests
[ https://issues.apache.org/jira/browse/MESOS-6475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone updated MESOS-6475: -- Sprint: Mesosphere Sprint 48 > Mesos Container Attach/Exec Unit Tests > -- > > Key: MESOS-6475 > URL: https://issues.apache.org/jira/browse/MESOS-6475 > Project: Mesos > Issue Type: Task >Reporter: Kevin Klues >Assignee: Kevin Klues > Labels: debugging, mesosphere > > Ideally, all unit tests should be written as the individual tasks that make > up this Epic are completed. However, sometime this doesn't always happen as > planned. > This ticket should not be closed and the Epic should not be considered > complete until all unit tests for all components have been written. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-6475) Mesos Container Attach/Exec Unit Tests
[ https://issues.apache.org/jira/browse/MESOS-6475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Klues updated MESOS-6475: --- Summary: Mesos Container Attach/Exec Unit Tests (was: Mesos Container Attach and Container Exec Unit Tests) > Mesos Container Attach/Exec Unit Tests > -- > > Key: MESOS-6475 > URL: https://issues.apache.org/jira/browse/MESOS-6475 > Project: Mesos > Issue Type: Task >Reporter: Kevin Klues >Assignee: Kevin Klues > Labels: debugging, mesosphere > > Ideally, all unit tests should be written as the individual tasks that make > up this Epic are completed. However, sometime this doesn't always happen as > planned. > This ticket should not be closed and the Epic should not be considered > complete until all unit tests for all components have been written. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
